Skip to content
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

Tag main as 0.31 canary #7332

Merged
merged 1 commit into from
Sep 30, 2024
Merged

Tag main as 0.31 canary #7332

merged 1 commit into from
Sep 30, 2024

Conversation

charlesBochet
Copy link
Member

@charlesBochet charlesBochet commented Sep 30, 2024

We are updating our git worklow.

Case 1: URGENT / PATCH
If you want to include something URGENT that cannot wait for the next release, you'll need to:

  • create a PR from the latest patch (right now v0.30.1)
  • create a new patch tag from this PR (would be v0.30.2 right now)
  • merge this PR in main so it's in 0.31 too

Case 2: REGULAR

  • Open a PR from main and merge it into main

I'm tagging main as v0.31.canary to make it clear!

@charlesBochet charlesBochet requested a review from Weiko September 30, 2024 09:29
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

This pull request updates the version number to '0.31.canary' across multiple package.json files, implementing a new git workflow for managing releases and tagging the main branch.

  • Updated version in package.json files for twenty-emails, twenty-front, twenty-server, twenty-ui, and twenty-website packages
  • Changed version from '0.30.0' to '0.31.canary' to indicate pre-release status for upcoming 0.31 release
  • Aligns with the described workflow for regular updates (Case 2) in the PR description
  • Consistent implementation across all modified files, with no critical issues or errors introduced

5 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings

@charlesBochet charlesBochet merged commit 1e4ed1e into main Sep 30, 2024
8 of 15 checks passed
@charlesBochet charlesBochet deleted the 0.31-canary branch September 30, 2024 09:42
harshit078 pushed a commit to harshit078/twenty that referenced this pull request Oct 14, 2024
We are updating our git worklow.

Case 1: **URGENT / PATCH**
If you want to include something URGENT that cannot wait for the next
release, you'll need to:
- create a PR from the latest patch (right now v0.30.1)
- create a new patch tag from this PR (would be v0.30.2 right now)
- merge this PR in main so it's in 0.31 too

Case 2: **REGULAR**
- Open a PR from main and merge it into main

I'm tagging main as v0.31.canary to make it clear!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants