Repository navigation
chore(release): remove the 1.0.0 release-as pins - #209
Draft
jeffdupont wants to merge 1 commit into
Draft
jeffdupont wants to merge 1 commit into
jeffdupont wants to merge 1 commit into
Conversation
1.0.0 has been published for every package, but release-as: 1.0.0 is still set in release-please-config.json, so release-please keeps re-proposing 1.0.0 in the open release PR. Without the pins, versions follow conventional commits. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
jeffdupont
force-pushed
the
jdupont/remove-release-as-pins
branch
from
November 6, 2026 22:33
93bd2aa to
11e6213
Compare
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 changed
Removes every
"release-as": "1.0.0"line (14 packages) fromrelease-please-config.json. Nothing else changes.Why
1.0.0 is published (tags
*-1.0.0, 2026-10-30), but the pins make release-please keep proposing 1.0.0 in the open release PR (#201). Without them, versions follow conventional commits.Proposed versions after merge
Derived from conventional commits since each package's
-1.0.0tag, touching its path. No breaking (!/BREAKING CHANGE) commits, so no 2.0.0.node-workspacebumps the@launchdarkly/ai-serverdependency (^1.0.0to^1.1.0)@launchdarkly/ai-*dependencyConfirmed with a
release-please17.11.2 dry run against this branch: 13 releases in total (six at 1.1.0, seven at 1.0.1), no 1.0.0 and no 2.0.0 proposals.🤖 Generated with Claude Code