Publish 4.0.7

[nknapp]

It would be nice if we could have a 4.0.7 release in the near future.

This would release the fixes for #1284, #1275, #1310, #1252, #1319

[nknapp]

I can't do it myself. Don't have the publishing rights.

[lawnsea]

Ok. I'm in an all day meeting today. I'll try to cut a release over the weekend.

On Fri, Feb 17, 2017, 2:13 AM Nils Knappmeier ***@***.***> wrote: I can't do it myself. Don't have the publishing rights. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#1312 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASFLnKBxhmYjbwU8AWjYmBTzgeg4HPKks5rdVangaJpZM4MD_Do> .

-- -Lon Ingram

[Turbo87]

@nknapp @lawnsea I'd suggest using TravisCI for the npm publish part. That way anyone with push permissions is automatically enabled to also publish to npm.

[nknapp]

It's not just npm, but also bower, rubygems and the handlebars-homepage.
Yes, it would be great to do this with TravisCI. It would greatly reduce overhead and let us publish much more often.

In the end, it is @wycats decision, because it is his repository. I mean: He may not want everybody who has push-access to also be able to publish.

[jeremykentbgross]

Any progress on the new release? Looks like a couple months and no action.

[nknapp]

Still waiting for @wycats to give me credentials...

[nknapp]

I have actually been thinking about publishing 4.0.7 under a different name, so that people could use it, but I don't like the thought of polluting the npm-registry with duplicate packages, and I still hope that @wycats will get back to me eventually.

[jeremykentbgross]

Has he not given any acknowledgement? Or is he just too busy/unconcerned?

[nknapp]

And I have answered to his mail... But I can't say anything about been busyness and concerns. He seems to have given some conference talks, so that may have taken his time. Am 28. April 2017 11:15:24 MESZ schrieb jeremykentbgross <notifications@github.com>:

…

Has he not given any acknowledgement? Or is he just too busy/unconcerned? -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #1312 (comment)

-- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

[wycats]

@nknapp @jeremykentbgross I'm really sorry. Let me take care of this ASAP.

[jeremykentbgross]

It's no problem. Much appreciated.

[wycats]

FYI I have given @nknapp the credentials 😄 👌

[nknapp]

I have now created a release 4.0.7 and it should have has been published to npm, rubygems and bower.

I still don't know how to upload the release to AWS. The URL http://builds.handlebarsjs.com.s3.amazonaws.com/handlebars.runtime-v4.0.7.js still returns an error.
And handlebarsjs.com needs to be updated as well as the jsfiddle link ( once AWS is up to date).

Or, we could just use unpkg.com.

[nknapp]

Can anybody give me information about how I can publish 4.0.7 to http://builds.handlebarsjs.com.s3.amazonaws.com/handlebars.runtime-v4.0.7.js?

@kpdecker @wycats @lawnsea @ErisDS

[kpdecker]

@nknapp email me at my username @ gmail and I'll work on getting you a copy of the creds that I (should still) have.

[nknapp]

@kpdecker pointed me to tasks/publish.js and the fact that the Travis-log contains branches: * (no branch). I think I found the problem.

We are not on the master branch anymore and the task publish:latest is only publishing to AWS when in the master branch. It does publish tagged versions, but well, only on master.

I'm going to make a PR to change that, but I'm uncertain how to test it without messing with the production downloads.

[nknapp]

I have managed to get a 4.0.8 release to AWS (by resetting the v4.0.8 tag forth and back).
The only thing that is missing now, is the update of the download-link on handlebarsjs.

wycats/handlebars-site#179 solves this, but I cannot merge it myself (due to access rights).

I can publish 4.0.7 and 4.0.6 to AWS as well, but I consider this less important than the current version, so I'm closing this issue now. If anybody needs this specific versions, please open an issue of comment here.

[nknapp]

4.0.8 is now referenced on handlebarsjs.com