Skip to content

chore(deps): use floating semver ranges for antelope modules - #16

Merged
Upd4ting merged 1 commit into
mainfrom
caret-antelope-deps
Jul 15, 2026
Merged

chore(deps): use floating semver ranges for antelope modules#16
Upd4ting merged 1 commit into
mainfrom
caret-antelope-deps

Conversation

@MrSociety404

@MrSociety404 MrSociety404 commented Jul 15, 2026

Copy link
Copy Markdown
Member

What

  • Reference antelope modules in playground/antelope.config.ts with a floating range (@antelopejs/api: 1.1.1^1.1.3).
  • Bump antelope dependencies to the latest published versions across all package.json files:
    • @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)
  • Refresh pnpm-lock.yaml.

Why

Now that @antelopejs/core 1.4.5 supports floating semver ranges in antelope.config, using ^x.y.z keeps antelope module versions current automatically instead of pinning a frozen version. Local modules are untouched.

Verified: pnpm build, tsc --noEmit, and biome check all pass.

Greptile Summary

This PR updates antelope module dependencies to their latest published versions and switches the playground/antelope.config.ts module reference from an exact pin to a caret range, taking advantage of floating semver support added in @antelopejs/core 1.4.5.

  • Bumps @antelopejs/interface-api to ^0.0.8 and @antelopejs/interface-core to ^0.0.6 in both package.json files; @antelopejs/interface-auth is left at ^0.0.5 as no newer version is available.
  • Switches @antelopejs/api in playground/antelope.config.ts from a pinned 1.1.1 to ^1.1.3 (note: 1.1.2 is skipped), moving to the current latest minor release.
  • pnpm-lock.yaml is 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

Filename Overview
package.json Bumps @antelopejs/interface-api from ^0.0.5 to ^0.0.8 and @antelopejs/interface-core from ^0.0.5 to ^0.0.6; @antelopejs/interface-auth is intentionally left at ^0.0.5.
playground/antelope.config.ts Switches @antelopejs/api from an exact pin (1.1.1) to a floating caret range (^1.1.3), skipping 1.1.2; consistent with @antelopejs/core 1.4.5 floating-range support.
playground/package.json Bumps @antelopejs/interface-core from ^0.0.5 to ^0.0.6 to match the root package.json; @antelopejs/interface-auth remains at ^0.0.5.
pnpm-lock.yaml Lockfile updated consistently: resolved versions and integrity hashes align with the new specifiers in all package.json files.

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)"]
Loading
%%{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)"]
Loading

Reviews (1): Last reviewed commit: "chore(deps): use floating semver ranges ..." | Re-trigger Greptile

@Upd4ting
Upd4ting merged commit 3a0733f into main Jul 15, 2026
3 checks passed
@Upd4ting
Upd4ting deleted the caret-antelope-deps branch July 15, 2026 21:43
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.

2 participants