Repository navigation
Conversation
Collaborator
Author
|
Superseded. The version rule now lives in #35: a change needs a new version only when what users install changes ( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
ci.ymlpasses the PR author (PR_AUTHOR) toscripts/check-changelog-heading.mjs.dependabot[bot], the script skips the "version greater than base" and release-notes checks. The CHANGELOG heading check still runs.pnpm-workspace.yamloverridessource-map-jsto^1.2.2(GHSA-68fv-2mgg-jv7q, Dependabot alert Clearing metric selection does not invalidate pending data requests #27). Dependabot's security update failed (security_update_not_possible: latest resolvable 1.2.1) because it couldn't move this transitive dev dependency (vitest > vite > postcss) in the pnpm lockfile; this follows the existing postcss/nanoid security floors.Why
Dependabot can't bump
package.jsonor write CHANGELOG entries, so each of its PRs failedtest (22)/test (24)until someone pushed a bump by hand (e.g. #34). Its updates now merge without publishing (publish.ymlskips a version already on npm) and ship with the next release.The exemption uses the PR author, not the branch name: anyone can push a
dependabot/...branch, but only Dependabot opens PRs asdependabot[bot].Verification
test/release-scripts.spec.ts: Dependabot may keep the base version; other authors (including a plaindependabotlogin) still must bump; the heading check still applies to Dependabot.pnpm test(113 passed),pnpm run build, and the heading check run locally with and withoutPR_AUTHOR=dependabot[bot].Impact
No change for human PRs. After merge, #34 can drop its manual bump and rely on the exemption.