Release 4.0.0-beta.1

[jsenko]

Part of #1214.

Trigger release.yaml on main. The POM is already at 4.0.0-beta.1-SNAPSHOT, and the workflow
understands pre-release versions: it will publish 4.0.0-beta.1, mark the GitHub release as a
prerelease, publish to npm under the beta dist-tag so latest stays on GA, and set the branch to
4.0.0-beta.2-SNAPSHOT afterwards.

Depends on the other items in #1214.

[jsenko]

One thing to fold into this release: the documented install coordinates still pin 3.1.1, which
is correct today but will be stale the moment 4.0.0-beta.1 is published.

• docs/index.md:34 — <version>3.1.1</version>
• docs/index.md:41 — implementation 'io.apitomy:apitomy-data-models:3.1.1'
• docs/getting-started.md:20 — <version>3.1.1</version>
• docs/getting-started.md:27 — implementation 'io.apitomy:apitomy-data-models:3.1.1'

These were deliberately left alone in #1221 rather than bumped early, so the published docs never
advertise an artifact that does not exist yet.

Worth deciding how they should read afterwards. A pre-release is not what most readers want from
a "getting started" page, so keeping 3.1.1 as the headline install and adding the beta
coordinates alongside it — clearly labelled, pointing at the migration guide — is probably better
than replacing it outright. The npm side needs the same treatment, since the beta publishes under
the beta dist-tag and a plain npm i @apitomy/data-models will keep resolving to 3.1.x.

[jsenko]

Release run: https://github.com/Apitomy/apitomy-data-models/actions/runs/36127712533

Step	Result
Version commit, tag, GitHub release	done: 4.0.0-beta.1 is a prerelease, and Latest stays 3.1.3
Maven Central	published
main moved to 4.0.0-beta.2-SNAPSHOT	done
npm	failed: ENEEDAUTH

Why npm failed. The job chose the beta dist-tag correctly, then the OIDC exchange gave it no credential. npm's trusted-publisher entry names npm-publish.yaml, but when that workflow is called from release.yaml through workflow_call, npm validates the calling workflow's name (see the npm docs, Trusted publishing, Troubleshooting). So it only works when npm-publish.yaml is run by hand. This predates the 4.x work: 3.1.1 and 3.1.3 were also published by manual runs of npm-publish.yaml.

To finish beta.1: run NPM Publish Workflow (npm-publish.yaml) from main with release-version: 4.0.0-beta.1, branch: 4.0.0-beta.1 (the tag, so it builds the released commit), and prerelease: true.

Permanent fix, on npmjs.com: add a second trusted publisher for @apitomy/data-models with workflow filename release.yaml (a package can have up to 10). Keep the npm-publish.yaml entry for manual retries. No workflow change is needed.

[jsenko]

Released. Maven Central and the GitHub prerelease came from the release run; npm from a manual run of npm-publish.yaml from the tag (https://github.com/Apitomy/apitomy-data-models/actions/runs/36133614547): beta → 4.0.0-beta.1, latest stays 3.1.3. main is at 4.0.0-beta.2-SNAPSHOT. The npmjs.com trusted-publisher entry for release.yaml is still needed so the next release publishes to npm without the manual step.