Skip to content

release: prepare 0.5.0 - #271

Open
sjungwon03 wants to merge 1 commit into
devfrom
chore/270-release-0-5-0
Open

release: prepare 0.5.0#271
sjungwon03 wants to merge 1 commit into
devfrom
chore/270-release-0-5-0

Conversation

@sjungwon03

Copy link
Copy Markdown
Member

Version, build numbers, and the store copy. No promotion — merging dev into
main is what releases.

before after
package.json version 0.4.1 0.5.0
expo.version 0.4.1 0.5.0
iOS build number 5 6
Android version code 4 5

Both stores refuse an upload whose build number is not higher than the last one
they saw, even for a rejected submission — so these move on every upload, not
every release.

What ships

Eighteen commits since v0.4.1: a timeline shaped for a phone, clip thumbnails,
titles, speed, transitions that render rather than only preview, colour, rotation
and position in the frame, audio waveforms, the AI reaching edits it previously
could not, and ads mediated by Unity LevelPlay rather than AdMob.

The four store note files are rewritten for that. The Play English copy had to be
cut: Play allows 500 characters and the full list ran to 574 — caught by the test
rather than by the console, which is the point of keeping this copy in the
repository.

Before promoting

  • The store privacy answers need updating. Five ad SDKs ship now where one
    did: Data Safety and App Privacy must declare device or other identifiers,
    collected by a third party, for advertising. Reviewers check that against the
    SDKs in the binary rather than against the form. mobile/RELEASING.md has the
    detail.
  • AppLovin is not bidding. Its adapter is in the binary, but the network has
    no instance configured for this app in the LevelPlay dashboard — as it stands
    the release ships an SDK that is declared and never asked to bid.
  • AdBanner has not been seen to render. Both placements serve through
    LevelPlay's Test Suite, which uses its own views; the app's own banner mounts a
    legacy view manager under the New Architecture, where the failure mode is a
    banner that never appears.

Closes #270

🤖 Generated with Claude Code

`dev` has carried a release's worth of work since v0.4.1 and none of it has been
promoted: a timeline shaped for a phone, thumbnails, titles, speed, transitions
that render rather than only preview, colour, rotation and position, audio
waveforms, the AI reaching edits it could not, and ads mediated by Unity
LevelPlay rather than AdMob.

The mobile build numbers rise with the version. Both stores refuse an upload
whose build number is not higher than the last one they saw, even for a
submission that was rejected, so `buildNumber` and `versionCode` move on every
upload rather than on every release.

The four store note files are rewritten for what actually ships. The Play
English copy is the one that had to be cut — Play allows 500 characters and the
full list ran to 574, which the test caught rather than the console.

Nothing here promotes anything. Merging `dev` into `main` is the release
trigger, and the Android job publishes to the production track with status
`completed` — live to every user the moment it lands.

Closes #270

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

@sjungwon03-ai sjungwon03-ai left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. Version and mobile build numbers are consistent and advanced from v0.4.1; store notes are within their platform limits. Exact-head CI passed, including iOS and Android native builds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

release: prepare 0.5.0

2 participants