-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Publish 4.0.7 #1312
Comments
I can't do it myself. Don't have the publishing rights. |
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
|
It's not just npm, but also bower, rubygems and the handlebars-homepage. 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. |
Any progress on the new release? Looks like a couple months and no action. |
Still waiting for @wycats to give me credentials... |
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. |
Has he not given any acknowledgement? Or is he just too busy/unconcerned? |
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.
|
@nknapp @jeremykentbgross I'm really sorry. Let me take care of this ASAP. |
It's no problem. Much appreciated. |
FYI I have given @nknapp the credentials 😄 👌 |
I have now created a release 4.0.7 and it 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. Or, we could just use unpkg.com. |
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? |
@nknapp email me at my username @ gmail and I'll work on getting you a copy of the creds that I (should still) have. |
@kpdecker pointed me to tasks/publish.js and the fact that the Travis-log contains We are not on the master branch anymore and the task I'm going to make a PR to change that, but I'm uncertain how to test it without messing with the production downloads. |
I have managed to get a 4.0.8 release to AWS (by resetting the v4.0.8 tag forth and back). 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. |
4.0.8 is now referenced on handlebarsjs.com |
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
The text was updated successfully, but these errors were encountered: