Skip to content

Conversation

legobeat
Copy link
Collaborator

@legobeat legobeat commented Sep 19, 2024

v0.6.3 is published on npm but package manifest is still at 0.6.2 on master. This aligns the manifest version to latest on npm.

NOTE: Actually published 0.6.3 is published from gitHead 7b4d8345934ad48d4cb1fd8fd2059fdb3a06f6da, which I can not seem to locate.

Actual diff

@thlorenz Any chance you still have access to that commit and able to push it as a v0.6.3 tag, so git tree and npm can match up?

Blocking

@legobeat legobeat marked this pull request as ready for review September 19, 2024 02:00
@legobeat legobeat changed the title v0.6.3 sync released v0.6.3 Sep 19, 2024
@legobeat legobeat requested a review from thlorenz September 19, 2024 02:16
@legobeat legobeat mentioned this pull request Sep 19, 2024
@legobeat legobeat requested a review from zertosh September 19, 2024 02:22
@thlorenz
Copy link
Owner

Any chance you still have access to that commit and able to push it as a v0.6.3 tag, so git tree and npm can match up?

Sorry, I don't, but PR and 0.6.4 follow up LGTM. Thanks!

@legobeat
Copy link
Collaborator Author

legobeat commented Sep 19, 2024

Sorry, I don't, but PR and 0.6.4 follow up LGTM. Thanks!

Ok, thanks for following up! I'll see if I can reconstruct it from the published version then, so we can get a tagged release were the sources match at least ^^

@legobeat legobeat merged commit c88d73f into master Sep 19, 2024
5 checks passed
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

Successfully merging this pull request may close these issues.

2 participants