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

⚠️ master branch is now alpha #1422

Closed
mtrezza opened this issue Oct 21, 2021 · 4 comments
Closed

⚠️ master branch is now alpha #1422

mtrezza opened this issue Oct 21, 2021 · 4 comments
Labels
type:meta Non-code issue

Comments

@mtrezza
Copy link
Member

mtrezza commented Oct 21, 2021

⚠️ New branch model

The master branch of this repository will be renamed alpha, becoming the new "default" branch. This is part of release automation to implement pre-releases (alpha, beta) to mature versions before official release.

✔️ Steps

  • If you have a clone locally or forked remotely, you will need to update your clones according to the GitHub instructions:

    git branch -m master alpha
    git fetch origin
    git branch -u origin/alpha alpha
    git remote set-head origin -a
    
  • When you open a pull request, make sure to open it against the new alpha branch.

  • For any repository you can look into the branch list to find out which branch the default branch is if you are unsure.

🌵Branch model

  • alpha: The working branch, replacing master; example release tag 1.0.0-alpha.1.
  • release: The official release; example release tag 1.0.0.
@mtrezza mtrezza added the type:ci CI related issue label Oct 21, 2021
@mtrezza mtrezza pinned this issue Oct 21, 2021
@mtrezza mtrezza added type:meta Non-code issue and removed type:ci CI related issue labels Oct 21, 2021
@mtrezza mtrezza changed the title ⚠️ master branch will be renamed alpha ⚠️ master branch is now alpha Oct 26, 2021
@mstniy
Copy link
Contributor

mstniy commented Oct 27, 2021

Note that the release branch is currently broken, as it tries to fetch the server using the master branch, which does not exist anymore.

@mtrezza
Copy link
Member Author

mtrezza commented Oct 27, 2021

Yes, that should be fixed on Nov 1st when alpha is merged into release. By "broken" you mean only the CI, right?

@mstniy
Copy link
Contributor

mstniy commented Oct 27, 2021

See package.json
It is marked as a dev dependency, so unless one tries to install the SDK with dev dependencies, it should be fine.

@mtrezza
Copy link
Member Author

mtrezza commented Oct 27, 2021

Yes, that has already been corrected on alpha and will be corrected on release by end of the week. I'd rather wait than correcting this manually now, because we want to try out the release automation that should create a PR to make a stable release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:meta Non-code issue
Projects
None yet
Development

No branches or pull requests

2 participants