Skip to content

release: @formio/js@5.3.6#12

Closed
johnformio wants to merge 2 commits into
masterfrom
monorepo-sync/v5.3.6
Closed

release: @formio/js@5.3.6#12
johnformio wants to merge 2 commits into
masterfrom
monorepo-sync/v5.3.6

Conversation

@johnformio

Copy link
Copy Markdown
Owner

Automated sync from formio/nirvana for @formio/js@5.3.6 (monorepo 90f9df78da).

After merging, an engineer will tag the release:

git fetch origin
git tag v5.3.6 origin/master
git push origin v5.3.6

Generated by gh-workflows/bin/sync-oss.mjs.

@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

Sync verify: @formio/js@5.3.6

Compared this PR head against formio/nirvana@90f9df78dad931abc97dca572ebc5b4209a3b994.

2 critical drift entries. 0 informational entries.

Critical drift means the PR contains content that did not come from nirvana. Either roll the offending changes into nirvana (so they ship via the next sync) or, if the file is OSS-owned, add it to .github/sync-verify.yml's exclude: list and re-trigger.

Critical — OSS contains changes not in nirvana

  • UNAUTHORIZED_OSS_FILE.md — extra file in OSS
  • 📦 [dependencies] @formio/core — nirvana=^2.6.6, OSS=^99.99.99

workflow run · adjust drift policy in .github/sync-verify.yml

@johnformio johnformio closed this Jun 4, 2026
@johnformio johnformio deleted the monorepo-sync/v5.3.6 branch June 4, 2026 17:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant