Skip to content

Sync main - #76

Merged
simoncodes-ca merged 4 commits into
developfrom
main
Sep 1, 2026
Merged

simoncodes-ca merged 4 commits into
developfrom
main

Conversation

@simoncodes-ca

Copy link
Copy Markdown
Owner

No description provided.

simoncodes-ca and others added 4 commits August 30, 2026 19:35
# [0.16.0](v0.15.0...v0.16.0) (2026-08-31)

### Bug Fixes

* **core:** build domain declarations before core's dts step ([1580002](1580002))
* **domain:** emit the branch-body brace pair for a Transloco consumer ([#70](#70)) ([7ac9ea6](7ac9ea6))
* **domain:** make Transloco to ICU conversion position-aware ([#67](#67)) ([d817a3f](d817a3f))
* **tsconfig:** repair project references so typecheck actually runs ([d4013ac](d4013ac))

### Features

* **protected-terms:** protect terms from translation across export, import, API, CLI, and UI ([551481d](551481d))
* **protected-terms:** store protected terms in a JSON file ([7574514](7574514))
npm rejects sigstore provenance from self-hosted runners with a 422, so
the release job can no longer honour the RUN_ON_VPS toggle. Pin it to
ubuntu-latest.

Add a workflow_dispatch republish job for the recovery case where
semantic-release tagged and pushed but the npm publish step failed, as
happened for v0.16.0. It lives in this workflow file because npm trusted
publishing authorizes by workflow filename.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ci: publish from a GitHub-hosted runner and add tag republish job
@simoncodes-ca
simoncodes-ca merged commit c52074b into develop Sep 1, 2026
6 checks passed
@simoncodes-ca
simoncodes-ca deleted the main branch September 1, 2026 07:25
@simoncodes-ca
simoncodes-ca restored the main branch September 1, 2026 16:44
@lingo-tracker-release

Copy link
Copy Markdown

🎉 This PR is included in version 0.17.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

This branch was previously deployed

1 inactive deployment
github-pages — b1c40313 Deployed Sep 1, 2026 by simoncodes-ca via Build & Deploy Docs #18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants