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

Figure out an appropriate release workflow #40

Open
pscanf opened this issue Nov 12, 2021 · 1 comment
Open

Figure out an appropriate release workflow #40

pscanf opened this issue Nov 12, 2021 · 1 comment
Labels
tech debt Technical debt
Projects
Milestone

Comments

@pscanf
Copy link
Member

pscanf commented Nov 12, 2021

Considerations:

  • I don't think it makes much sense to use semver for the app
  • if we need/want to publish some packages to npm, they'll have to use semver
@pscanf pscanf added the tech debt Technical debt label Nov 12, 2021
@pscanf pscanf added this to the 1.0.0 milestone Nov 12, 2021
@pscanf pscanf added this to To do in 1.0.0 Nov 12, 2021
@pavinduLakshan
Copy link

As I believe, semver is suitable for managing dev artifacts. The calver may be a more appropriate alternative for a consumer app. Companies like Jetbrains are already using it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tech debt Technical debt
Projects
1.0.0
To do
Development

No branches or pull requests

2 participants