Repository navigation
Prepare 2.0.0-beta.1 - #83
Merged
ottonomy merged 2 commits intoOct 21, 2026
Merged
Conversation
Set the package version to 2.0.0-beta.1 for a preliminary release ahead of 2.0.0. The changelog keeps a single 2.0.0 Unreleased entry; the beta gets no entry of its own. - Write changelog dates as ISO dates, matching the other DCC repos. - Fold 1.0.0-beta.9, which never reached npm, into 1.0.0-beta.10, and note that earlier preliminary releases are not recorded. - Rename the README migration section to "Migration from earlier 1.x" and point the changelog link at its new anchor. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pull_request trigger only matched pull requests based on main, so a pull request stacked on another branch was not guaranteed a CI run. Pushes still run CI on main only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Stacked on #81 — review and merge that first.
Prepares the first 2.0 preliminary release,
2.0.0-beta.1, to test the release end to end before 2.0.0.package.jsonversion is now2.0.0-beta.1. The changelog keeps a single2.0.0 - Unreleasedentry; the beta gets no entry of its own, so the eventual 2.0.0 entry reads against 1.0.0-beta.11.2025-12-15), matching issuer-registry-client, open-badges-context, signing-service and transaction-service.ci.ymlnow runs on pull requests to any branch, not onlymain, so every pull request in a stack gets CI. Pushes still run CI onmainonly.Docs, version and CI trigger only; no code changes, so nothing beyond CI to run.
After the stack merges to
mainPublish a GitHub release per RELEASING.md: tag
v2.0.0-beta.1created on publish, targetmain, pre-release ticked, latest unticked. That runspublish.yml, which publishes to the npmbetadist-tag and leaveslateston 1.0.0-beta.11.This is the first run of
publish.yml, so the npm trusted-publisher registration described in RELEASING.md needs to be in place first.🤖 Generated with Claude Code