Bad release maneuver

[douglasduteil]

Hi @thgreasi
I saw you release a new ui-sortable version (0.12.5) "by hand" !
Did you bypass the auto publishing on purpose ?

[thgreasi]

Yes, I did it by hand...
One day after merging #165 the new release didn't show up.
Everything was OK on travis and I even issued a rebuild, just in case (I`m guessing that travis is creating the release, is it?).

Any ideas what caused that?

[douglasduteil]

One day after merging #165 the new release didn't show up.

Yes my bad I made a "breaking change" in the publisher system to force sources tags releases !
angular-ui/angular-ui-publisher@23e4c37
So the gh-pages branch is only updated on master branch
And the 'bower' branch with the releases are made on /^src\d+\.\d+\.\d+.*$/ branches

So you just need to create a tag on github named src0.12.5 to make Travis update the bower branch and publish a v0.12.5 version

[thgreasi]

Do I need to tag with -a or a lightweight tag is enough?
Moreover, will it mess things up if I start tagging past commits with src*.*.* (it might help with grunt-conventional-changelog)?

PS: never used git tag before. Hope I will not demolish the repo...

[douglasduteil]

Just renaming the tag you made on github seems to work... Wait for it

[douglasduteil]

K when Travis was rejected when it tried to push the new tag (see L357)

[douglasduteil]

I'm deleting the tag by hand with a git push origin :v0.12.5
Then I'll force a restart of Travis with a new build by recreating a src0.12.5 tag

[douglasduteil]

Wait for it

[douglasduteil]

Legendary !

[thgreasi]

@douglasduteil so next time i will just:

git tag -a src0.12.6
git push --tags

???

[douglasduteil]

No next time you just use github to Create a release, and you name if src0.12.6 yeah
Travis will do the rest :)

[douglasduteil]

I just saw the last releases 👍
The auto-publishing is working like a charm. What do you think of it @thgreasi ? Is it bothering you ?