-
Notifications
You must be signed in to change notification settings - Fork 205
ci: add gha to publish v5 alpha pkgs #2305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR adds a GitHub Actions workflow for publishing v5 alpha packages. The workflow enables manual publishing of v5 alpha releases through a workflow dispatch trigger, with built-in dry-run capability for safety.
Key Changes:
- New GitHub Actions workflow for publishing v5 alpha packages with manual trigger and dry-run mode
- Updates to the docs-site submodule commit reference
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/publish-v5-alpha.yml |
Implements automated v5 alpha package publishing with version increment, NPM publish, and git tagging |
docs-site |
Updates submodule reference to latest commit |
🌿 Documentation Preview
|
| fetch-depth: "0" | ||
| submodules: "recursive" | ||
|
|
||
| - name: Free up disk space |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this required on every run?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good question. i just copied it from the other publishing action.
looks like @blakecduncan added it a couple of months ago b/c the other GHA was running out of disk space: 0c1b48a
| CURRENT_VERSION=$(node -p "require('./lerna.json').version") | ||
| echo "Current version: $CURRENT_VERSION" | ||
| # Calculate next version (increment the number after the last dot) | ||
| NEXT_VERSION=$(echo "$CURRENT_VERSION" | awk -F. -v OFS=. '{$NF++; print}') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use semvar here instead of manually bumping the version to avoid mismatch between dryrun/actual run versions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good idea! updated.
Pull Request Checklist
yarn test)sitefolder, and guidelines for updating/adding docs can be found in the contribution guide)feat!: breaking change)yarn lint:check) and fix any issues? (yarn lint:write)PR-Codex overview
This PR introduces a new GitHub Actions workflow named
Publish V5 Alpha Packages, which facilitates the publishing of alpha versions of packages. It includes steps for setup, version incrementing, and publishing, with options for dry runs and automated version injection.Detailed summary
.github/workflows/publish-v5-alpha.yml.workflow_dispatchfor manual triggering.moldy/v5-basebranch.