chore: add beta release workflow action #4798
Open
+98
−0
Conversation
This file contains 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
This reverts commit c329489.
Branch preview |
rubencarvalho
commented
Oct 2, 2024
| - name: Set Git identity | ||
| run: | | ||
| git config --global user.email "rcarvalho@adobe.com" | ||
| git config --global user.name "Ruben Carvalho" |
There was a problem hiding this comment.
We will create a team Git identity.
rubencarvalho
commented
Oct 2, 2024
|
|
||
| - name: Configure NPM for Lerna publish | ||
| env: | ||
| NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} |
There was a problem hiding this comment.
We will create a team npm account and respective token. (to avoid using my personal)
Lighthouse scores
What is this?Lighthouse scores comparing the documentation site built from the PR ("Branch") to that of the production documentation site ("Latest") and the build currently on Transfer Size
Request Count
|
Tachometer resultsCurrently, no packages are changed by this PR... |
Pull Request Test Coverage Report for Build 11145229192Details
💛 - Coveralls |
Rajdeepc
reviewed
Oct 2, 2024
| @@ -13,6 +13,20 @@ This page provides comprehensive information on versioning, public APIs, browser | |||
|
|
|||
| Starting from version 1.0.0, Spectrum Web Components follows semantic versioning ([semver](https://semver.org/)). We regularly release patch versions, which do not contain breaking changes. When a breaking change occurs, it will be done in a major version release to avoid breaking existing applications depending on the old version. Major version releases will be communicated in advance, and migration guides will be provided. | |||
|
|
|||
| ### Beta versions | |||
|
|
|||
| To provide early access to upcoming releases, we maintain a beta tag that points to the next minor version. The beta tag will always correspond to the next minor version incremented from the latest stable release. For example, if the latest tagged release is `1.2.1`, the beta tag will be `1.3.0-beta.0`. | |||
There was a problem hiding this comment.
Is there a way we can spin up a parallel beta site with the existing netlify account?
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.
Description
This PR introduces a new GitHub Actions workflow to automate the publishing of beta releases whenever changes are merged into the
mainbranch. The beta releases are configured to always point to the next minor version.Related issue(s)
Motivation and context
We're aiming to shorten feedback loops with teams, allowing consumers to test upcoming features and fixes before the official release.
This also moves us closer to a full CI/CD pipeline and will allow us to play around the idea of dry-run builds for upcoming releases.
Types of changes
Checklist
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against
main.