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

Push the changes in the v1.2.0 branch instead of main for the next minor release #43

Closed
AnirudhPanda opened this issue Oct 4, 2021 · 1 comment
Labels
notice wontfix This will not be worked on

Comments

@AnirudhPanda
Copy link
Member

AnirudhPanda commented Oct 4, 2021

As our main branch is getting updated almost every day and it is also a good practice to make changes to a release branch and then merge the two branches at regular intervals eg; 15 days and then publish it to npm.

Please push the new changes to v1.2.0 branch instead of main and let's build this package the Open Source Way

@AnirudhPanda AnirudhPanda added wontfix This will not be worked on notice labels Oct 4, 2021
@AnirudhPanda AnirudhPanda pinned this issue Oct 4, 2021
@AnirudhPanda AnirudhPanda changed the title Push the changes in the v1.1.0 branch instead of main for the next minor release Push the changes in the v1.2.0 branch instead of main for the next minor release Oct 10, 2021
@AnirudhPanda AnirudhPanda unpinned this issue Nov 3, 2021
@AnirudhPanda
Copy link
Member Author

NEW VERSION PUBLISHED with #98

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
notice wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant