ci: tag protection ruleset, dependency + provenance badges (v0.5.5) - #11
Merged
Conversation
- Add tag-protection ruleset (.github/rulesets/tags.json) blocking deletion, force-push, and update on refs/tags/v*.*.*. The ruleset is also active server-side; the JSON is the canonical re-apply spec. - README: add Libraries.io dependency status badge and an npm-provenance badge alongside the existing CI / Codecov / CodeQL set. - Bump to v0.5.5.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
2 participants
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.
Summary
refs/tags/v*.*.*) blocking deletion, force-push, and tag updates. The ruleset is active server-side;.github/rulesets/tags.jsonis the canonical re-apply spec forgh api ... -X POST --input.src/changes).Repo settings adjusted out-of-band
The following settings were also flipped on at the repo level (not in this diff):
delete_branch_on_merge: true— auto-clean merged PR branchesallow_update_branch: true— let contributors sync a PR branch withmainfrom the GitHub UITest plan
v0.5.5on the squash commit, push tag, confirmrelease.ymlpublishes to npm with provenance and creates the GitHub Release from the matching CHANGELOG section.