[phndiaye]

Brings master into the Ember 6.12 upgrade and moves the addon onto the @upfluence/oss-components 4.0.0-beta.3 release, so the stack is green and ready for a 4.0.0 beta.

• Merges master (31914b6, the OSS asset-map adapter from Adopt the @upfluence/oss-components asset-map adapter #288) into feature/ember-upgrade-4-to-7.
• Depends on @upfluence/oss-components 4.0.0-beta.3 and publishes under the beta dist-tag.

No version bump and no tag in this PR.

Conflict resolutions

• package.json: kept the feature side for every version (Ember 6.12 toolchain, @upfluence/oss-components 4.0.0-beta.2 at merge time, "version": "3.17.3"). Master only bumped oss-components to ^3.100.0. broccoli-asset-rev ^3.0.0 was already in devDependencies on the feature side, so the asset-map adapter has what it needs.
• pnpm-workspace.yaml (add/add): kept master's version, which declares packages: ['.'] and still has the same onlyBuiltDependencies: ['@upfluence/oss-components'] entry the feature side had.
• pnpm-lock.yaml: took the feature side and regenerated it with pnpm install.

These master changes merged without conflicts and are kept as they are:

• ember-cli-build.js: fingerprint asset map plus injectAssetMap from @upfluence/oss-components/build/classic-asset-map.cjs, wrapped around the feature side's maybeEmbroider call. 4.0.0-beta.3 ships build/classic-asset-map.cjs.
• tests/dummy/app/index.html and tests/index.html: the upfluence:asset-map meta tag and the shared Font Awesome stylesheet.

Ported to Ember 6.12 conventions

Nothing to port. Master only changed build config, HTML entry points and package files since the merge-base (6a6b98f), and I checked all of them for legacy patterns (inject as service, array prototype extensions, ember-data imports, store.find, this.get, ember-ajax). None turned up.

Dependencies

• @upfluence/oss-components devDependency: 4.0.0-beta.2 → 4.0.0-beta.3 (exact).
• @upfluence/oss-components peerDependency: ^3.x → ^4.0.0-beta.0.
• publishConfig.tag: "beta" added next to the existing GitHub Packages registry. The release job runs npm publish on v* tags, and this makes sure a 4.0.0 beta does not become latest.
• pnpm-lock.yaml: @upfluence/oss-components resolves to the single registry version 4.0.0-beta.3, with no git or codeload pins.

Release guard

• .github/workflows/ci.yml: the release job's Trigger upfluence-web/deploy step now has if: ${{ !contains(github.ref, '-') }}. Prerelease tags such as v4.0.0-beta.0 still run npm publish (under the beta dist-tag), but they no longer dispatch the upfluence-web staging Bump Dependency workflow. Stable tags still do.
• Once a stable 4.0.0 is cut, publishConfig.tag: "beta" must be removed, or 4.0.0 would also go out under beta.

Verification

• pnpm install: ok
• pnpm lint:js: ok
• pnpm prettier '**/*.hbs' -c: ok
• pnpm tsc --noEmit: ok
• pnpm test:ember: 374 tests, 373 pass, 1 skipped, 0 failures. The test build includes injectAssetMap.
• CI on bd95aed (with the release guard): Lint and Tests pass, Release and Deploy are skipped as expected.
• pnpm lint:hbs (ember-template-lint, not run in CI) reports 22 errors (require-input-label and similar). They come from the feature branch, not from this PR, and I left them alone.
• I could not run a local production build because the disk was full. CI only builds production on master.

🤖 Generated with Claude Code