Hey, thanks for merging #67. We're using the node24 update now, but we had to pin to a commit on main (2003922) since v1.1.0 predates the fix.
Just a heads up; this is a problem for anyone following GitHub's SHA-pinning guidance. Dependabot and Renovate can't resolve updates without a tagged release, so consumers won't pick up the node24 fix through normal tooling before the June 2 forced migration.
Would you mind cutting a release? More frequent tags going forward would also help, even if changes are small.
Hey, thanks for merging #67. We're using the node24 update now, but we had to pin to a commit on main (
2003922) since v1.1.0 predates the fix.Just a heads up; this is a problem for anyone following GitHub's SHA-pinning guidance. Dependabot and Renovate can't resolve updates without a tagged release, so consumers won't pick up the node24 fix through normal tooling before the June 2 forced migration.
Would you mind cutting a release? More frequent tags going forward would also help, even if changes are small.