feat: pre-release workflow #2910
Conversation
|
WalkthroughThis update introduces several new GitHub Actions workflows for managing pre-release modes, including processes to enter and exit pre-release modes and handle beta and canary versions. Additionally, it updates scripts in Changes
Sequence DiagramssequenceDiagram
participant Developer as Developer
participant GitHub as GitHub Actions
participant Repository as Repository
Developer->>+GitHub: Manual dispatch for pre-release mode
GitHub->>GitHub: Trigger enter-pre-release-mode workflow
GitHub->>Repository: Check out branch
GitHub->>Repository: Install dependencies
GitHub->>Repository: Perform pre-release setup
GitHub->>Repository: Push changes
Note over GitHub,Repository: Pre-release mode is entered
Developer->>GitHub: Push new changes to pre-release branch
GitHub->>Repository: Trigger pre-release workflow
GitHub->>Repository: Check for changesets and packages
GitHub->>Repository: Create pre-release PRs
GitHub->>NPM: Publish beta versions to NPM
Note over GitHub,Repository: Pre-release updates and versions published
Recent review detailsConfiguration used: .coderabbit.yaml Files selected for processing (3)
Additional comments not posted (4)
Warning Review ran into problemsProblemsGit: Failed to clone repository. Please run the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review Details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Files selected for processing (6)
- .changeset/config.json (1 hunks)
- .github/workflows/enter-pre-release-mode.yaml (1 hunks)
- .github/workflows/exit-pre-release.yaml (1 hunks)
- .github/workflows/pre-release.yaml (1 hunks)
- .github/workflows/release.yaml (2 hunks)
- package.json (1 hunks)
Files skipped from review due to trivial changes (1)
- .changeset/config.json
Files skipped from review as they are similar to previous changes (5)
- .github/workflows/enter-pre-release-mode.yaml
- .github/workflows/exit-pre-release.yaml
- .github/workflows/pre-release.yaml
- .github/workflows/release.yaml
- package.json
There was a problem hiding this comment.
Actionable comments posted: 0
Out of diff range and nitpick comments (1)
apps/docs/components/sandpack/use-sandpack.ts (1)
[!TIP]
Codebase VerificationThe verification process has identified an inconsistency in the versioning of the
@nextui-org/reactdependency within theuse-sandpack.tsfile. It is currently set to "latest" instead of the intended "canary" version. This appears to be an oversight that needs correction.
- File and Location:
apps/docs/components/sandpack/use-sandpack.ts- Suggested Correction: Update the version of
@nextui-org/reactfrom "latest" to "canary" to maintain consistency across the project.Analysis chain
Line range hint
147-163: Update dependencies to use the "canary" version consistently.Ensure that all dependencies are correctly updated across the entire project to reflect these changes.
Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify that all dependencies across the project use the "canary" version where applicable. # Test: Search for dependency declarations not using the "canary" version. Expect: No occurrences outside the specified ones. rg --type ts $'@nextui-org/.*"latest"'Length of output: 120
Script:
#!/bin/bash # Description: Search for all occurrences of @nextui-org dependencies to check their versioning across the project. # Test: List all @nextui-org dependencies and their versions. rg --type ts '@nextui-org/.*"'Length of output: 184525
Review Details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Files selected for processing (2)
- apps/docs/components/sandpack/use-sandpack.ts (2 hunks)
- apps/docs/preinstall.js (1 hunks)
Additional comments not posted (1)
apps/docs/preinstall.js (1)
29-29: Ensure that thenpm showcommand handles potential errors.
Assumptions:
canarymainbranch only stores as a snapshot (current production)pre.jsonshouldn't be inmainbranch📝 Description
Pre-release
Example (beta/release-next):
Example (canary): similar to above one
Enter Pre-releaes
canaryorbeta/release-nextpre.jsonwill be created after the workflowExit Pre-release
canaryorbeta/release-nextpre.jsonwill be removed after the workflowAdditional Info
read:userandrepo:statuspermissions for exit prereleaseSummary by CodeRabbit
New Features
package.jsonfor managing changeset versions (canaryandbeta).Enhancements