Repository navigation
chore: prepare email metadata patch 0.52.1 - #340
Merged
Merged
Conversation
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.
Publish an email-metadata patch using the verified npm account contact hello@m1ngshum.com. This stamps 0.52.1 without changing runtime code, dependencies, or the tracked placeholder version.
Keep companion projects on their tested 0.52.0 baseline for this metadata-only patch. Existing local work and commit noreply settings remain untouched. Required CI and release dogfood must pass before publication; verify new-version and top-level npm maintainer metadata afterward. Historical versions remain unchanged.