chore(deps): use floating semver ranges for antelope modules - #16
Merged
Conversation
Upd4ting
approved these changes
Jul 15, 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.
What
playground/antelope.config.tswith a floating range (@antelopejs/api:1.1.1→^1.1.3).package.jsonfiles:@antelopejs/interface-api:^0.0.5→^0.0.8@antelopejs/interface-core:^0.0.5→^0.0.6@antelopejs/interface-auth: unchanged (already at latest^0.0.5)pnpm-lock.yaml.Why
Now that
@antelopejs/core1.4.5 supports floating semver ranges inantelope.config, using^x.y.zkeeps antelope module versions current automatically instead of pinning a frozen version. Local modules are untouched.Verified:
pnpm build,tsc --noEmit, andbiome checkall pass.Greptile Summary
This PR updates antelope module dependencies to their latest published versions and switches the
playground/antelope.config.tsmodule reference from an exact pin to a caret range, taking advantage of floating semver support added in@antelopejs/core1.4.5.@antelopejs/interface-apito^0.0.8and@antelopejs/interface-coreto^0.0.6in bothpackage.jsonfiles;@antelopejs/interface-authis left at^0.0.5as no newer version is available.@antelopejs/apiinplayground/antelope.config.tsfrom a pinned1.1.1to^1.1.3(note:1.1.2is skipped), moving to the current latest minor release.pnpm-lock.yamlis fully regenerated with consistent resolved versions and integrity hashes.Confidence Score: 5/5
Safe to merge — all changes are dependency version bumps with a consistent, regenerated lockfile and no logic changes.
The diff is limited to version specifier updates in two package.json files, a config version string change, and the corresponding lockfile regeneration. The resolved peer dependency graph in the lockfile is internally consistent (interface-auth@0.0.5 resolves correctly against api@0.0.8 and core@0.0.6 within the declared >=0.0.3 <1.0.0 peer range). No application logic, tests, or build configuration were modified.
No files require special attention.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[package.json / playground/package.json] -->|declares| B["@antelopejs/interface-api ^0.0.8"] A -->|declares| C["@antelopejs/interface-core ^0.0.6"] A -->|declares| D["@antelopejs/interface-auth ^0.0.5 (unchanged)"] B --> E[pnpm-lock.yaml resolves 0.0.8] C --> F[pnpm-lock.yaml resolves 0.0.6] D --> G["pnpm-lock.yaml resolves 0.0.5 (peer: api@0.0.8, core@0.0.6)"] H[playground/antelope.config.ts] -->|module source| I["@antelopejs/api ^1.1.3 (was 1.1.1)"]%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%% flowchart TD A[package.json / playground/package.json] -->|declares| B["@antelopejs/interface-api ^0.0.8"] A -->|declares| C["@antelopejs/interface-core ^0.0.6"] A -->|declares| D["@antelopejs/interface-auth ^0.0.5 (unchanged)"] B --> E[pnpm-lock.yaml resolves 0.0.8] C --> F[pnpm-lock.yaml resolves 0.0.6] D --> G["pnpm-lock.yaml resolves 0.0.5 (peer: api@0.0.8, core@0.0.6)"] H[playground/antelope.config.ts] -->|module source| I["@antelopejs/api ^1.1.3 (was 1.1.1)"]Reviews (1): Last reviewed commit: "chore(deps): use floating semver ranges ..." | Re-trigger Greptile