Require signed releases and complete shared OAuth metadata - #18
Merged
Conversation
bherila
changed the title
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.
Require GitHub-verified annotated tag signatures before npm or Packagist publication. Expose validated OAuth provider metadata so consumer apps can remove their remaining provider-config duplication. Also override esbuild to 0.28.2 and remove the current low-severity development-server advisory.\n\nValidation: 44 PHP tests / 107 assertions; Composer strict validation; TypeScript check; package build; actionlint. The existing unsigned v0.5.1 tag remains immutable until signed v0.5.2 is published and consumers update.