release: 0.1.36 - #39
Merged
Merged
Conversation
Three commits landed after 0.1.35 and none of them bumped the version, so nothing would have been released and the published browser would stay built against the engine 0.1.35 resolved: 5fd2e24 stop committing lockfiles de0fac7 pin @solidjs/signals 367f594 the headless host action does not need a secret The first is the one that matters. 0.1.35 was built with a lockfile pinning ps-blitz 0.4.4; master now resolves 0.4.6, which is the difference between a browser that can intercept a router click and reach a TLS 1.3 host and one that cannot. The second changes the frontend bundle. The third touches only a composite action consumed at `@master`, and would not have justified a release on its own. This is the same gap as ps-blitz 0.4.6: master moved past its last release and the version said otherwise, so a consumer resolving by version got code nobody had shipped.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three commits landed after
b3de85a release: 0.1.35with no bump, so no release fires and the published browser stays built against the engine 0.1.35 resolved.5fd2e24stop committing lockfilesde0fac7pin @solidjs/signals367f594headless host token@masterThe first is the substantive one: 0.4.6 is the difference between a browser that can intercept a router click and reach a TLS 1.3 host, and one that cannot.
Same gap as ps-blitz 0.4.6 earlier today: master moved past its last release while the version said otherwise.