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

document release process #22

Open
mr-c opened this issue Jun 13, 2020 · 3 comments
Open

document release process #22

mr-c opened this issue Jun 13, 2020 · 3 comments
Assignees

Comments

@mr-c
Copy link
Member

mr-c commented Jun 13, 2020

Also, shouldn't we be using a v prefix on the tags to distinguish from non-release tags?

@mr-c
Copy link
Member Author

mr-c commented Jun 13, 2020

Ah, I had not updated the version number in cwl_utils/__meta__.py (other projects I contribute to get their version number from the tag automatically). We should document the release procedure

@mr-c mr-c changed the title deployment of 0.5 failed document release process Jun 13, 2020
@illusional
Copy link
Collaborator

Hey @mr-c , I was just going by what you had done previously. Happy for v prefix, or even X.X.X (using semver maybe).

I put it in meta so you can get the version from code (without the package manager). I can comment it soon, but yeah generally:

  • bump version on meta
  • got tag with same version

@mr-c
Copy link
Member Author

mr-c commented Dec 11, 2020

@illusional Thanks again for setting that up. Twice (versions 0.8 and 0.9) now I've tagged and pushed to main but nothing happens ; I've manually uploaded those in the mean time

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

No branches or pull requests

2 participants