Skip to content

Add git tags for the published versions #482

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

Closed
a14n opened this issue May 15, 2015 · 4 comments
Closed

Add git tags for the published versions #482

a14n opened this issue May 15, 2015 · 4 comments
Labels
contributions-welcome Contributions welcome to help resolve this (the resolution is expected to be clear from the issue) P2 A bug or feature request we're likely to work on type-infra A repository infrastructure change or enhancement

Comments

@a14n
Copy link
Contributor

a14n commented May 15, 2015

On the tags page we should see the tags corresponding to the versions on pub.

git tag v0.0.1+10 $sha
git push origin --tags
@sethladd
Copy link
Contributor

probably true. There's a grinder task that tries to be the release workflow. Can you help update that or create a new grinder task that can do all the things we want to do when releasing, including pushing to pub? That would be a big help.

@seaneagan
Copy link
Contributor

I think eventually it can look like:

@Task
release([String releaseType = 'build']) {
  new PubApp.global('den').run[['bump', releaseType];
  Pub.publish();
}

grind release:patch

but first we'll need:

seaneagan/unscripted#21
google/grinder.dart#116
google/grinder.dart#203

@sethladd
Copy link
Contributor

Thanks for the analysis. Please land those patches so we can automate the whole thing :)

@sethladd sethladd added contributions-welcome Contributions welcome to help resolve this (the resolution is expected to be clear from the issue) P2 A bug or feature request we're likely to work on type-infra A repository infrastructure change or enhancement labels May 23, 2015
@keertip
Copy link
Collaborator

keertip commented Jun 25, 2015

We have a manual process for now. Can automate when all the necessary bits are in place.

@keertip keertip closed this as completed Jun 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contributions-welcome Contributions welcome to help resolve this (the resolution is expected to be clear from the issue) P2 A bug or feature request we're likely to work on type-infra A repository infrastructure change or enhancement
Projects
None yet
Development

No branches or pull requests

4 participants