Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,11 @@ jobs:
# --no-increment: the version already lives in package.json, reviewed
# and merged through a pull request.
# --no-git: the tag is pushed by the maintainer; CI never writes to git.
args=(--ci --no-increment --no-git)
# -VV: logs the output of release-it's own commands, including npm's
# `+ <name>@<version>` once the registry accepts the package. `-V`
# only logs hook output. npm's notices go to stderr, which release-it
# shows only when a command fails.
args=(--ci --no-increment --no-git -VV)
if [ "${{ github.event_name }}" != 'push' ]; then
args+=(--dry-run)
echo 'Rehearsal run — nothing will be tagged or published.'
Expand Down
5 changes: 5 additions & 0 deletions RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,11 @@ version is not already on npm and that `CHANGELOG.md` has a section for it;
publishes to npm with provenance; and
creates the GitHub Release with that section as its body.

The Publish step logs `+ @gmisoftware/react-native-pay@<version>` when npm
accepts the package. The version can take a few minutes more to show up on the
registry: 0.1.0 appeared about 5 minutes after the workflow finished. Don't
re-run the workflow or re-push the tag while you wait.

The iOS podspec reads its version from `package.json`, so there is no second
version to keep in sync.

Expand Down
Loading