Repository navigation
chore(deps): pause routine version PRs during Wirebound v1.2 stabilization - #62
Merged
Merged
Conversation
This was referenced Oct 28, 2026
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.
Temporarily set
open-pull-requests-limit: 0for the repository's two scheduled Dependabot version-update ecosystems (npm,github-actions). This prevents routine weekly version-update PR churn while the maintainer intentionally defers dependency upgrades until Wirebound v1.2.0 is stable.Security update PRs remain permitted via Dependabot's separate security-update limit; vulnerability alerts/security remediation are not intentionally disabled. Scheduled update entries stay documented. To resume version update PRs after stabilization, restore each limit to
10.Config-only change; no runtime, lockfile, dependency or Windows effects. Propose merge after CI and then close obsolete routine version PRs (#27–#32, #36, #60); do not close explicit security update PRs.