Repository navigation
ci: add automated beta SDK release track - #1394
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1394 +/- ##
========================================
Coverage 89.41% 89.41%
========================================
Files 439 439
Lines 21082 21082
Branches 10327 9990 -337
========================================
Hits 18851 18851
Misses 2231 2231
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
developerkunal
self-requested a review
September 23, 2026 08:51
harshithRai
approved these changes
Sep 25, 2026
This was referenced Oct 5, 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
3 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.
Changes
Adds an automated beta SDK release track alongside the existing stable track
New files:
.github/actions/compute-next-version/action.yml- composite action that derives the next version from git tags (no state file needed). For the beta track: latest stable v6.3.0 → v6.4.0-beta.1, auto-incrementing -beta.N on each release. Scopes tag lookups to the current major line by reading .version, so legacy v5 tags are never treated as candidates..github/workflows/beta-autorelease.yml- triggers on PR merge into the beta branch. Computes the next beta version, stamps.version,package.json,src/management/version.ts, andCHANGELOG.md, builds and publishes to npm with--provenance --tag beta, creates a GitHub API-signed release commit (shows as Verified), and publishes a GitHub prerelease. Serialized with a concurrency group to prevent version races.Modified files:
.github/workflows/ci.yml- adds beta to push/PR branch triggers so lint, build, test, and coverage run on the beta branch.AGENTS.md- documents the beta track workflow for AI coding agents: versioning logic, structured commit message format, files owned by automation, dual-PR requirement for hand-written code.CONTRIBUTING.md- documents the beta track for human contributors: consumer opt-in (npm install auth0@beta), the / squash commit message format, and what the automation does end-to-end.How the two tracks work:
Because v6.4.0-beta.N sorts before v6.4.0 in semver, a plain npm install auth0 never selects a beta version. Consumers must opt in explicitly: npm install auth0@beta
This PR is infrastructure only, it changes nothing on master today and is inert until the beta branch is created and the upstream Fern beta generation target is wired.
References
Testing
Checklist