Skip to content

chore(next): release 0.13.0-next - #126

Merged
taraxvoid merged 1 commit into
nextfrom
release-please--branches--next--components--voidflow
Oct 8, 2026
Merged

taraxvoid merged 1 commit into
nextfrom
release-please--branches--next--components--voidflow

Conversation

@ravenflight-releases

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.13.0-next (2026-10-06)

Features

  • add conventional-commits release method (#27) (3cd5a86)
  • branch-based release channels (next prerelease, maintenance branches, floating v0) (#105) (978f1db)
  • branch-env-map: single-environment mode (main to prod, PRs to preview) (#91) (bc50b96)
  • justfile: add lint-only validation target (b0fbc23)
  • manage branch rulesets as code (#98) (8f9c64b)
  • npm: also publish unscoped voidflow mirror (#69) (8cebb32)
  • npm: publish @taraxvoid/voidflow via trusted publishing (#67) (46b8ebd), closes #65
  • playwright: add shared definePreviewConfig helper (#64) (#66) (4901738)
  • release: migrate to release-please (#71) (ecf3961)
  • resolve-env: add reusable workflow to expose deploy env as a job output (413cab4)
  • shared lefthook config for the site stack (#103) (98ea3cd)
  • shared Renovate preset (#104) (649d2b8)
  • ship check-licenses as a package bin (#97) (4041a59)
  • site-ci.yml: add GITLEAKS_LICENSE secret since organizations require it (5000ccc)
  • site-ci.yml: add optional GITLEAKS_LICENSE secret for gitleaks Organization plan (4504d72)
  • site-ci.yml: add support for Playwright installation without OS-level browser dependencies on self-hosted runners (8fcac78)
  • site-ci: package-manager, e2e-extra-paths, build-env inputs; skip missing scripts (#90) (cd10551)
  • site-ci: single-environment input for main-only sites (#102) (7be76fd)
  • support JSR as npm alternative (#78) (75b68ce)
  • unlighthouse: add shared Unlighthouse CI runner (#63) (b8a2798)

Bug Fixes

  • also run validate on pushes (#48) (50ede94)
  • ci.yml: disable uv dependency cache since repo has no lockfile/requirements to key it on (#37) (82f81a4)
  • ci: make npm publish steps idempotent (#87) (5ad4f10)
  • ci: resolve e2e base branch on push events (#96) (28e1465)
  • cloudflare-deploy: sanitize deployment-url output for multi-custom-domain deploys (#49) (d4a1eee)
  • cloudflare-deploy: warn when --config bypasses the build's deploy redirect (#85) (9b09c1c)
  • docs: prerelease tags carry the -next suffix (#109) (1c74e3a)
  • improve Playwright cache invalidation (#22) (f8d863b)
  • invalidate py cache (b5106e4)
  • just use github actions a la site-ci.yml instead of using just validate (de40c3b)
  • just use github actions a la site-ci.yml instead of using just validate (#68) (2c90d50)
  • lefthook: pre-commit unit step honors test:unit:precommit (#110) (0be17d7)
  • move JSR publish above NPM to fix issue when npm dirties the tree (6560f87)
  • release.yml: pass GH_TOKEN through to just validate (#28) (fb573d7)
  • release.yml: pin --tag-pattern for the auto-bump path (#38) (1ea0abb)
  • release: publish to npm with NPM_TOKEN until npm accepts immutable OIDC subjects (#76) (87a407b)
  • release: split into PR-then-tag flow, main is PR-only (#30) (dea2940)
  • resolve-env: use local action path to satisfy zizmor's unpinned-uses policy (a3c210b)
  • scope minimumReleaseAgeExcludes under [install] (#111) (9869f82)
  • site-ci: scan secrets with OSS gitleaks binary (#95) (1fb27ea)
  • tag-release.yml: tolerate squash-merge's " (#NN)" suffix (#33) (665b9f3)
  • tag-release: handle merge-commit release messages (fb8e067)
  • tag-release: handle merge-commit release messages (ba6a6c9)
  • unlighthouse: launch Chrome with --no-sandbox in CI (#114) (67daebb)

This PR was generated with Release Please. See documentation.

@taraxvoid
taraxvoid merged commit 896ef20 into next Oct 8, 2026
2 checks passed
@taraxvoid
taraxvoid deleted the release-please--branches--next--components--voidflow branch October 8, 2026 04:55
@ravenflight-releases

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant