Skip to content

v0.7.1

  • v0.7.1
  • fb80fb5

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    GPG key ID: B5690EEEBB952194
    Verified
    Learn about vigilant mode

  • Choose a tag to compare

    View all tags
v0.7.1: fix(release): bump to 0.7.1 to recover from partial 0.7.0 publish (#106)
  • v0.7.1
  • fb80fb5

  • Choose a tag to compare

    View all tags

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    GPG key ID: B5690EEEBB952194
    Verified
    Learn about vigilant mode
@GerMoren GerMoren tagged this 24 May 12:26 
Release 0.7.0 succeeded for @junando/core, ingest, webhook, worker but
failed for create-junando-app because scripts/verify-tarball.js still
referenced template/_gitignore at the template root. The previous fix
that moved .gitignore into app/ updated sync-template.js and scaffold.ts
but missed verify-tarball.js. prepublishOnly only runs during publish,
so the local build did not catch it.

Two fixes here:

1. verify-tarball.js: update required paths to template/app/_gitignore
   and template/app/.env.example to match the new layout. Also update
   the mustShip assertion and header comment.

2. Bump all 5 publishables (root + core + ingest + webhook + worker +
   create-junando-app) from 0.7.0 to 0.7.1. The first four are already
   live on npm at 0.7.0, so trying to republish that version would 403
   and abort the workflow before reaching create-junando-app. Bumping
   the whole set preserves the lockstep convention documented in
   docs/compatibility.md.

docs/compatibility.md regenerated via pnpm run docs:compat.

Verified locally:
- 25/25 tests verde
- oxlint clean
- docs:compat:check passes
- node scripts/verify-tarball.js OK (17 files, 8.7 KB)

Refs #76
Assets 2
Loading