Tags

v1.2.7

v1.2.6

v1.2.5

v1.2.4

v1.2.3

v1.2.2

v1.2.1

v1.2.0

v1.1.2

v1.1.2 — first release on the auto-bump-from-tag flow

Functionally identical to v1.1.1: same code, no behavior change.
Cut to validate the new release ergonomics end-to-end.

What changed in the release flow (donations MR !29, sha 0235033):
  Before: developer manually bumps 4 manifests on a branch, opens MR,
          merges, tags. Forgetting step 1 wedges every security:* job.
  After:  `git tag vX.Y.Z && git push origin vX.Y.Z`. The CI auto-bumps
          every manifest from CI_COMMIT_TAG before any gate or build
          runs. Main keeps manifests at the LAST released version
          indefinitely; the tag IS the version.

This tag is the first to use the new flow:
  - Main HEAD (0235033) has manifests at 1.1.1 (the LAST released
    version) — intentionally not pre-bumped to 1.1.2.
  - The CI's bump step (scripts/bump-version-from-tag.sh) writes
    1.1.2 into all 4 manifests in-pipeline.
  - Security gates + publish run against the bumped tree.
  - Post-publish, main stays at 1.1.1 — next release just tags
    again.

If the v1.1.2 pipeline goes green end-to-end (security: 4 jobs, then
publish:node:* x3, publish:python, publish:r2), the flow is proven.

go/donations-embed/v1.1.2

v1.1.1

v1.1.1 — operational release

Bundles up everything merged after v1.1.0:
- Plan 9A R2 publish job for the donations-embed CDN bundle
- Customer-facing FQDN scrub (payments.1stflock.com)
- §9.1 deferred work + §9.4 management/CMS RBAC plumbing
- CI fixes: arch-aware gitleaks, openssl install for r2 dry-run,
  docker runner default tag, smoke:e2e:full auto-run, YAML
  indentation correction on the 3 security stages
- Manifest version bump 1.1.0 → 1.1.1 across all 4 packages
  (node/donations-embed, donations-embed-node, donations-embed-react,
  python/donations-embed) so the tag-version-match gate passes

go/donations-embed/v1.1.1

v1.1.0

Donations embed v1.1.0 — env-aware SDKs

v1.0.1

v1.0.1 — Python wheel hotfix

* python: re-include donations_embed/models/webhook_test.py
  (production Pydantic model for POST /v1/embed/webhooks/test)
  that was over-aggressively excluded by **/*_test.py glob in
  v1.0.0. Customers can now `from donations_embed.models.webhook_test
  import WebhookTestRequest` as documented.

* node: lockstep version bump to 1.0.1 (no behavioral change).
  React wrapper's ^1.0.0 peer-dep on @1st-flock/donations-embed
  already accepts 1.0.1.

* ci: tarball-audit gate no longer treats _test.py suffix as a
  pytest convention. Real tests in this repo use test_*.py prefix.

Customer impact: pip install -U onefirstflock-donations-embed
fixes ModuleNotFoundError on the webhook test endpoint client.

go/donations-embed/v1.0.1

go/donations-embed/v1.0.0

release: donations-embed v1.0.0

First public release of the 1st Flock Donations Embed SDK family.

Packages published:
  - @1st-flock/donations-embed         (browser web component)
  - @1st-flock/donations-embed-react   (React wrapper)
  - @1st-flock/donations-embed-node    (server-side Node SDK)
  - onefirstflock-donations-embed      (Python SDK)
  - gitlab.com/1st-flock/donations/go/donations-embed   (Go module)

v1.0.0

release: donations-embed v1.0.0

First public release of the 1st Flock Donations Embed SDK family.

Packages published:
  - @1st-flock/donations-embed         (browser web component)
  - @1st-flock/donations-embed-react   (React wrapper)
  - @1st-flock/donations-embed-node    (server-side Node SDK)
  - onefirstflock-donations-embed      (Python SDK)
  - gitlab.com/1st-flock/donations/go/donations-embed   (Go module)