Skip to content

Commit a9e284a

Browse files
committed
Merge branch 'main' into codex/clarify-team-ownership-model
2 parents ba26ac5 + e06d82b commit a9e284a

92 files changed

Lines changed: 2597 additions & 289 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.changeset/README.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,8 @@ Pick the affected packages, the bump type (patch / minor / major), and write a o
2727
The repo is currently in changesets **prerelease mode** with the `alpha` tag (see `.changeset/pre.json`). While in this mode:
2828

2929
- `changeset version` cuts versions like `0.1.0-alpha.0`, `0.1.0-alpha.1`, …
30+
- Public packages are in one fixed group, so an alpha train uses the same
31+
version across `@zitadel/cli`, SDKs, components, and generated API packages.
3032
- `changeset publish` publishes them under the **`alpha`** npm dist-tag, **not** `latest`. So `npm install @zitadel/cli` keeps resolving the last stable release; consumers opt into prereleases with `@zitadel/cli@alpha`.
3133
- A package that has never had a stable release is published to `latest` on its first publish (changesets behaviour), then to `alpha` thereafter until it has a stable release.
3234

@@ -57,7 +59,14 @@ short-lived OIDC credentials, but npm only accepts public provenance
5759
attestations from public source repositories. Re-enable provenance when
5860
`zitadel/nextgen` is public.
5961

60-
The Go server binary is **not** managed by changesets — it is released with `goreleaser` through the manual [`release.yml`](../.github/workflows/release.yml) workflow while the repo is pre-release. See [docs/adrs/002-multi-package-release-strategy.md](../docs/adrs/002-multi-package-release-strategy.md).
62+
Changesets does not build the Go server binary. During alpha, `release-npm.yml`
63+
uses the lockstep npm version as the release train version, creates `v<version>`,
64+
and then runs GoReleaser so the server image and binaries publish into the same
65+
GitHub Release. The manual [`release.yml`](../.github/workflows/release.yml)
66+
workflow remains a server snapshot/fallback path. See
67+
[docs/adrs/002-multi-package-release-strategy.md](../docs/adrs/002-multi-package-release-strategy.md)
68+
and
69+
[docs/adrs/023-lockstep-alpha-release-train.md](../docs/adrs/023-lockstep-alpha-release-train.md).
6170

6271
## Licensing reminder
6372

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@zitadel/api": patch
3+
---
4+
5+
Fix `configureZitadel()` so its state survives when more than one copy of `@zitadel/api/config` ends up loaded — the standalone components bundle inlines its own copy, and dual-package hazards / duplicate `node_modules` trees in a monorepo can load a second copy alongside the app's. Previously each module instance held its own `let currentProject`, so a `configureZitadel()` call in one was invisible to `getZitadelConfig()` in another and the components silently saw no config. The slot now lives on `globalThis` under a `Symbol.for(...)` key, which the global symbol registry resolves to the same symbol identity in every copy of the module evaluated in the same JS realm — separate realms (iframes, Node `vm` contexts, worker threads) still have their own registries.
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
"@zitadel/components": minor
3+
---
4+
5+
Allow configuring `<zitadel-login>` and `<zitadel-logout>` declaratively from HTML via `project-id`, `proxy-path`, and `url` attributes, so the components work on a plain page without JS or `configureZitadel()`. Configuration resolves in this order, highest first: the `project` property, then the `configureZitadel()` global, then the HTML attributes. The existing JS paths still win — the attributes are the no-JS fallback.
6+
7+
Also fix the standalone bundle so it loads in a browser: it was built for Node and emitted an `import "node:module"` that browsers cannot resolve. It is now built for the browser, so `dist/standalone.mjs` is genuinely self-contained.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@zitadel/components": minor
3+
---
4+
5+
Add a standalone browser bundle (`dist/standalone.mjs`) so the components work on a plain HTML page via `<script type="module">` with no import map or bundler. Exposed via the `./standalone` export and `unpkg`/`jsdelivr`.

.changeset/config.json

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,19 @@
22
"$schema": "https://unpkg.com/@changesets/config@latest/schema.json",
33
"changelog": ["@changesets/changelog-github", { "repo": "zitadel/nextgen" }],
44
"commit": false,
5-
"fixed": [],
5+
"fixed": [
6+
[
7+
"@zitadel/cli",
8+
"@zitadel/api",
9+
"@zitadel/components",
10+
"@zitadel/sdk-core",
11+
"@zitadel/sdk-next",
12+
"@zitadel/sdk-nuxt",
13+
"@zitadel/sdk-react",
14+
"@zitadel/sdk-vue",
15+
"@zitadel/sdk-angular"
16+
]
17+
],
618
"linked": [],
719
"access": "public",
820
"baseBranch": "main",

.changeset/lockstep-alpha-train.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@zitadel/cli": patch
3+
---
4+
5+
Derive alpha local runtime images from the installed CLI version, pin generated SDK dependencies to the same alpha train, and emit exact-version follow-up commands for reproducible tester reports.

.changeset/pre.json

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,18 +28,25 @@
2828
"changesets": [
2929
"add-spa-sdks",
3030
"align-alpha-sdk-dependency",
31+
"api-config-global-slot",
3132
"cli-drop-unused-flows",
3233
"cli-remove-claim-logic",
3334
"cli-scaffold-middleware",
3435
"cli-server-owned-schema-flow",
3536
"components-atoms-and-orchestrator",
37+
"components-audit-lit-tidy",
38+
"components-declarative-config",
3639
"components-orval-wireup",
3740
"components-replace-ui-lit-placeholders",
41+
"components-standalone-bundle",
3842
"consumer-journey-credential-flow",
3943
"design-tokens-and-ui-react",
4044
"fix-cli-nx-ci",
4145
"fix-release-pnpm-setup",
46+
"lockstep-alpha-train",
4247
"passkey-end-to-end-flow",
48+
"quiet-doctor-scaffold",
49+
"register-profile-field-labels",
4350
"slow-lines-grin",
4451
"smooth-playwright-journey",
4552
"soft-local-dev",
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
"@zitadel/components": patch
3+
---
4+
5+
Add English labels for the `givenName`, `familyName`, and `dateOfBirth`
6+
fields the default register step now collects.

.changeset/try-depot-runners.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
---
2+
---
3+
4+
Try Depot Ubuntu 24.04 runners for GitHub Actions workflows.

.github/instructions/consumer-journey.instructions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ demo-app e2e suite.
1212
- Produce package artifacts with `corepack pnpm --dir <package> pack` and keep
1313
tarball verification for required package presence plus unresolved
1414
`catalog:` or `workspace:` dependency specs.
15-
- Pack only the six public Zitadel packages. Private support packages such as
15+
- Pack only the public Zitadel packages. Private support packages such as
1616
design tokens must not be uploaded or published to Verdaccio.
1717
- Keep Verdaccio proxying npmjs for third-party dependencies while publishing
1818
Zitadel tarballs under both `alpha` and `latest`.

0 commit comments

Comments
 (0)