[5.x] Antlers config backwards compatibility#14146
Merged
jasonvarga merged 7 commits into5.xfrom Mar 4, 2026
Merged
Conversation
# Conflicts: # tests/Antlers/ScratchTest.php
jasonvarga
changed the title
ryanmitchell
added a commit
to ryanmitchell/statamic-translation-manager
that referenced
this pull request
Mar 11, 2026
* build: update dependencies, especially Statamic 6 No efforts to get code updated for Statamic 6 yet, just the composer dependencies and enough modification to get tests running again. * build: remove unused use statements. * feat: Statamic 6 compatible main page Also includes Vite for building components. Probably some work still to do to get the dist files built at the right time/place. Baby steps. * fix: tooling for generating dist JS file * fix: add semantic release automation * fix: missing dist files * fix: downgrade semantic release The 11 version had an issue with pre-release (alpha) numbering. At least according to AI. * fix: configure semantic-release with main (stable) and alpha (prerelease) branches Resolves ERELEASEBRANCHES error by making main the stable release branch and adding a separate alpha branch for pre-release versions. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: use Vue component for index page Previously, this Vue component had been on a test route, but now that it has feature parity with the original, it can fill the original place. * fix: include Statamic components per official doc * fix: remove old Blade version of index page * fix: missing cp nav menu icon * fix: bring Vite and structure in alignment to doc * fix: more component compiling fixing Specifically, deduplicating JS file outputs and removing the external bit from the Vite config, which was maybe blowing things up. * fix: compact layout for selecting translation lang * fix: add/edit/delete functionality for terms * doc: update requirements list * fix: obsolete edit blade removed * fix: blueprint scan index converted to Vue 3 * fix: blade template scan convert to Vue * fix: ellipsis throwing off translation key interpretation * fix: remove obsolete scan blade template * ci: ensure dist is up to date It's easy to forget that the dist files (addon.js at present) weren't rebuilt for a release. This workflow compares a freshly build dist to the one in the commit. If they're the same, it's all good. If not, then a warning message is provided. * fix: forgotten dist file (didn't get published) * build: update Statamic dependency version to 6.5 This avoids the breaking change introduced in 6.4 (which was somewhat improved in 6.5). 6.4 Release Notes: https://github.com/statamic/cms/releases/tag/v6.4.0 6.5 Release Notes: https://github.com/statamic/cms/releases/tag/v6.5.0 Specific fix to avoid breaking change: statamic/cms#14146 * doc: minor wording change * build: update action to include composer dependencies Because the Statami vite plugin is used, and comes from the Statamic CMS composer package, that package needs to be installed so it can be referenced. * fix: update the dist Well, I guess now we know that the dist files check GitHub action works. :-) * build: update composer dependencies Also including the composer.lock so that there's less chance of difference between the developer's build, and the CI's build. * doc: Note the min required Statamic as 6.5 * standardize vite, tidy up * use our release process * remove composer lock for test suite * update test flow --------- Co-authored-by: Jared Carlow <jcarlow@fmamfg.org> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR makes the heavy-handed-but-necessary breaking change in recent releases less heavy-handed and less breaking.
This PR adds a simplified parse method that will safely extract config placeholders before handing off to Antlers.
Now if you have things like
'{{ config:foo:bar }}'in your yaml files, you don't need to addfoo:barto the allow list.(More complicated usage like chaining modifiers will still require opt-ins.)
It also brings back the full config array when you are in an Antlers view.