Repository navigation
Fix the README links in the release notes - #10
Merged
Merged
Conversation
…s headings that exist
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
What and why
The release notes linked to
#first-launch-of-a-build-that-isnt-notarized,#linuxand#windows, which aren't README headings any more. They now point at#macos-a-build-that-isnt-notarized,#linux-a-secret-serviceand#windows-smartscreen.How I checked it
### macOS: a build that isn't notarized,### Linux: a Secret Service,### Windows: SmartScreen).Left out
Nothing.