Repository navigation
Version Packages - #498
Merged
Merged
Version Packages#498
Conversation
Contributor
SCC Complexity Analysis
|
jose-filho-azion
approved these changes
Nov 11, 2026
patrick-menoti-azion
approved these changes
Nov 11, 2026
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
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@aziontech/[email protected]
Minor Changes
#490
40d1833Thanks @jose-filho-azion! - Support the Azion API v6 config in the same packages.@aziontech/config: a config withversion: 6is now validated and processed into a v6 manifest. v3 and v4 are unchanged, and a config withoutversionis still the v4 one. v6 changes the publishing model: Save creates a Draft version and publishing is a separate step, so the config declaresenvironmentsanddeployments(the environment and deployment policies are required) and workloads withbindings(a binding references an environment and a deployment by name). Adds the build, applications (rules, cache settings, function instances and device groups), functions (with bindings), purge, storage, connectors, firewall, WAF, network lists and custom pages.validateConfig,processConfig,validateManifestandconvertJsonConfigToObjectaccept v6, anddefineConfigtypes the config asAzionConfigV6. The v3 and v4 manifests now carry the API version. The v6 API has noactivein its resources, so the v6 config and manifest do not have it, and thecreateSPARulesandcreateMPARuleshelpers no longer writeactive: true(it is the default of the v4 and v3 rules).@aziontech/presets: every preset now provides its v6 config inconfigs[6](nitrohas no v3 config, as it did not exist on v3).configremains the default (v4) config.@aziontech/[email protected]
Minor Changes
#490
40d1833Thanks @jose-filho-azion! - Support the Azion API v6 config in the same packages.@aziontech/config: a config withversion: 6is now validated and processed into a v6 manifest. v3 and v4 are unchanged, and a config withoutversionis still the v4 one. v6 changes the publishing model: Save creates a Draft version and publishing is a separate step, so the config declaresenvironmentsanddeployments(the environment and deployment policies are required) and workloads withbindings(a binding references an environment and a deployment by name). Adds the build, applications (rules, cache settings, function instances and device groups), functions (with bindings), purge, storage, connectors, firewall, WAF, network lists and custom pages.validateConfig,processConfig,validateManifestandconvertJsonConfigToObjectaccept v6, anddefineConfigtypes the config asAzionConfigV6. The v3 and v4 manifests now carry the API version. The v6 API has noactivein its resources, so the v6 config and manifest do not have it, and thecreateSPARulesandcreateMPARuleshelpers no longer writeactive: true(it is the default of the v4 and v3 rules).@aziontech/presets: every preset now provides its v6 config inconfigs[6](nitrohas no v3 config, as it did not exist on v3).configremains the default (v4) config.Patch Changes
#490
40d1833Thanks @jose-filho-azion! - Fix thenuxtpreset prebuild reading a stale or missing manifest. Nuxt >= 4.6 builds intonode_modules/.cache/nuxt/.nuxtwhen.nuxtalready exists, so.nuxt/manifest/metais no longer reliable. The manifest is now read from.output/public/_nuxt/builds/metafirst, then from the cache dir and.nuxt, picking the file thatlatest.jsonreferences.#490
40d1833Thanks @jose-filho-azion! - Fix the regex of the "Redirect to index.html for Subpaths" rule of thenuxt,svelteandnitropresets (v4 and v6 configs). It matched files such as/logo.pngand skipped the paths without extension such as/about, because of[sS]*(instead of[\s\S]*) and an unescaped.. It now matches only the paths that do not end with/and have no file extension.Updated dependencies [
40d1833]:@aziontech/[email protected]
Patch Changes
40d1833,40d1833,40d1833]: