chore: release main by github-actions[bot] · Pull Request #112 · AreteA4/arete

github-actions · 2026-05-31T16:34:03Z

🤖 I have created a release beep boop

arete-idl: 0.0.2

0.0.2 (2026-06-17)

Features

support Codama root-node IDLs and variable discriminators (1ffcf84)
support Codama root-node IDLs in arete-idl (5317df4)

Bug Fixes

surface errors for unsupported Codama IDL features instead of silent fallbacks (f6fd10c)
Update ore idls (108a66f)

a4-cli: 0.1.4

0.1.4 (2026-06-17)

Miscellaneous Chores

a4-cli: Synchronize arete versions

Dependencies

The following workspace dependencies were updated
- dependencies
  - arete-interpreter bumped from 0.1.3 to 0.1.4
  - arete-idl bumped from 0.0.1 to 0.0.2

arete: 0.1.4

0.1.4 (2026-06-17)

Miscellaneous Chores

arete: Synchronize arete versions

Dependencies

The following workspace dependencies were updated
- dependencies
  - arete-interpreter bumped from 0.1.3 to 0.1.4
  - arete-macros bumped from 0.1.3 to 0.1.4
  - arete-server bumped from 0.1.3 to 0.1.4

arete-sdk: 0.1.4

0.1.4 (2026-06-17)

Features

support Codama root-node IDLs and variable discriminators (1ffcf84)

arete-interpreter: 0.1.4

0.1.4 (2026-06-17)

Features

support Codama root-node IDLs and variable discriminators (1ffcf84)

Bug Fixes

avoid generated SDK type collisions (3ebb266)
preserve primitive rust field types (1beb2ce)
process resolver mutations asynchronously (b7ace34)
remove redundant integer normalization branch (0cad96a)
retry and profile runtime resolver misses (dfbd8c9)

Dependencies

The following workspace dependencies were updated
- dependencies
  - arete-macros bumped from 0.1.3 to 0.1.4
  - arete-idl bumped from 0.0.1 to 0.0.2

arete-macros: 0.1.4

0.1.4 (2026-06-17)

Features

support Codama root-node IDLs and variable discriminators (1ffcf84)

Bug Fixes

batch resolver mutations with primary updates (38cab89)
gRPC connection (0586474)
handle variable and embedded account discriminators in macros (e744bf7)
process resolver mutations asynchronously (b7ace34)

Dependencies

The following workspace dependencies were updated
- dependencies
  - arete-idl bumped from 0.0.1 to 0.0.2

arete-mcp: 0.1.4

0.1.4 (2026-06-17)

Miscellaneous Chores

arete-mcp: Synchronize arete versions

arete-server: 0.1.4

0.1.4 (2026-06-17)

Miscellaneous Chores

arete-server: Synchronize arete versions

Dependencies

The following workspace dependencies were updated
- dependencies
  - arete-interpreter bumped from 0.1.3 to 0.1.4

a4-npm: 0.1.4

0.1.4 (2026-06-17)

Bug Fixes

add manual npm publish recovery tooling (1563f85)

arete-mcp-npm: 0.1.4

0.1.4 (2026-06-17)

Bug Fixes

add manual npm publish recovery tooling (1563f85)

arete-react: 0.1.4

0.1.4 (2026-06-17)

Bug Fixes

add manual npm publish recovery tooling (1563f85)

Dependencies

The following workspace dependencies were updated
- dependencies
  - @usearete/sdk bumped from ^0.1.3 to ^0.1.4

arete-typescript: 0.1.4

0.1.4 (2026-06-17)

Bug Fixes

add manual npm publish recovery tooling (1563f85)

This PR was generated with Release Please. See documentation.

vercel · 2026-05-31T16:34:07Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
arete-docs	Ready	Preview, Comment	Jun 17, 2026 9:54pm

greptile-apps · 2026-05-31T16:37:12Z

Greptile Summary

Release Please–generated version bump across all workspace crates and packages: Rust crates move from 0.1.3 → 0.1.4 (except arete-idl which goes 0.0.1 → 0.0.2), and TypeScript/npm packages follow the same 0.1.3 → 0.1.4 cadence.

Rust crates: arete-idl, arete-macros, arete-interpreter, arete-a4-sdk, arete-server, arete-mcp, arete, and a4-cli all receive version bumps and updated intra-workspace dependency pins.
TypeScript/npm packages: @usearete/sdk, @usearete/react, @usearete/a4, and @usearete/mcp are each bumped to 0.1.4.
CHANGELOGs: All packages receive new release entries; arete-idl/CHANGELOG.md has a version ordering anomaly where 0.0.2 is followed by a pre-existing 0.1.6 entry.

Confidence Score: 4/5

Safe to merge for local/path builds; three arete-sdk version pins remain at 0.1.3 and will publish stale minimum-version constraints to crates.io

rust/arete-mcp/Cargo.toml, arete/Cargo.toml, and cli/Cargo.toml all use the arete-sdk alias for arete-a4-sdk but leave the version field at 0.1.3 while the underlying crate ships as 0.1.4; path resolution means CI passes, but published crates will declare compatibility with the older release

rust/arete-mcp/Cargo.toml (newly identified missed bump), arete/Cargo.toml, and cli/Cargo.toml

Important Files Changed

Filename	Overview
rust/arete-mcp/Cargo.toml	Version bumped to 0.1.4 but arete-sdk (arete-a4-sdk) dependency still declares version = "0.1.3"
arete-idl/CHANGELOG.md	New 0.0.2 entry prepended to a file that already has 0.1.6 as its next entry, creating an inverted semver ordering
arete/Cargo.toml	All internal deps bumped except arete-sdk alias which remains at 0.1.3
cli/Cargo.toml	arete-interpreter and arete-idl deps correctly bumped; arete-sdk still at 0.1.3
interpreter/Cargo.toml	Version bumped to 0.1.4; arete-macros and arete-idl deps correctly updated
arete-macros/Cargo.toml	Version bumped to 0.1.4; arete-idl dep correctly updated to 0.0.2
rust/arete-a4-sdk/Cargo.toml	Version bumped from 0.1.3 to 0.1.4; no dependency changes needed
rust/arete-server/Cargo.toml	Version bumped to 0.1.4; arete-interpreter dep correctly updated
typescript/react/package-lock.json	Root package entry still references @usearete/sdk ^0.0.1 while package.json was updated to ^0.1.4
typescript/core/package.json	Version bumped to 0.1.4; no other changes
.release-please-manifest.json	All package versions updated in manifest correctly
Cargo.lock	Lock file updated to reflect all Rust crate version bumps

_{Reviews (3): Last reviewed commit: "chore: release main" | Re-trigger Greptile}

greptile-apps · 2026-05-31T16:37:15Z

+arete-server = { version = "0.1.4", path = "../rust/arete-server", optional = true }

 # SDK - Rust client for connecting to Arete servers
 arete-sdk = { package = "arete-a4-sdk", version = "0.1.3", path = "../rust/arete-a4-sdk", optional = true }


The arete-sdk alias for arete-a4-sdk was not bumped from 0.1.3 to 0.1.4 alongside all other internal dependencies in this release. The same stale constraint appears in cli/Cargo.toml line 38. Because path overrides the registry lookup during local builds, this passes CI, but when published to crates.io the version field becomes the authoritative constraint that downstream consumers see — leaving it at 0.1.3 while the actual crate ships as 0.1.4 creates a misleading declaration of the minimum compatible version.

Suggested change

arete-sdk = { package = "arete-a4-sdk", version = "0.1.3", path = "../rust/arete-a4-sdk", optional = true }

arete-sdk = { package = "arete-a4-sdk", version = "0.1.4", path = "../rust/arete-a4-sdk", optional = true }

Prompt To Fix With AI

This is a comment left during a code review. Path: arete/Cargo.toml Line: 25 Comment: The `arete-sdk` alias for `arete-a4-sdk` was not bumped from `0.1.3` to `0.1.4` alongside all other internal dependencies in this release. The same stale constraint appears in `cli/Cargo.toml` line 38. Because `path` overrides the registry lookup during local builds, this passes CI, but when published to crates.io the version field becomes the authoritative constraint that downstream consumers see — leaving it at 0.1.3 while the actual crate ships as 0.1.4 creates a misleading declaration of the minimum compatible version. ```suggestion arete-sdk = { package = "arete-a4-sdk", version = "0.1.4", path = "../rust/arete-a4-sdk", optional = true } ``` How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-05-31T16:37:16Z

-arete-interpreter = { version = "0.1.3", path = "../interpreter" }
+arete-interpreter = { version = "0.1.4", path = "../interpreter" }
 arete-idl = { path = "../arete-idl", version = "0.0.1" }
 arete-sdk = { package = "arete-a4-sdk", path = "../rust/arete-a4-sdk", version = "0.1.3" }


Same missed bump: arete-sdk still declares version = "0.1.3" while arete-a4-sdk is being released as 0.1.4 in this PR. arete-interpreter on the same file was correctly updated; this dependency was overlooked.

Suggested change

arete-sdk = { package = "arete-a4-sdk", path = "../rust/arete-a4-sdk", version = "0.1.3" }

arete-sdk = { package = "arete-a4-sdk", path = "../rust/arete-a4-sdk", version = "0.1.4" }

Prompt To Fix With AI

This is a comment left during a code review. Path: cli/Cargo.toml Line: 38 Comment: Same missed bump: `arete-sdk` still declares `version = "0.1.3"` while `arete-a4-sdk` is being released as 0.1.4 in this PR. `arete-interpreter` on the same file was correctly updated; this dependency was overlooked. ```suggestion arete-sdk = { package = "arete-a4-sdk", path = "../rust/arete-a4-sdk", version = "0.1.4" } ``` How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-05-31T16:37:17Z

+      "version": "0.1.4",
      "license": "MIT",
      "dependencies": {
        "@usearete/sdk": "^0.0.1"


Lock file root entry out of sync with package.json

The root "" entry in package-lock.json still records "@usearete/sdk": "^0.0.1", but package.json was updated to "^0.1.4". npm v7+ regenerates the lock file's root package section from package.json, so the next npm install on a clean tree would write ^0.1.4 there automatically — but shipping an already-desynchronised lock file can confuse tooling that diffs or audits the two files. This looks like the lock file wasn't regenerated after package.json was edited.

Prompt To Fix With AI

This is a comment left during a code review. Path: typescript/react/package-lock.json Line: 12 Comment: **Lock file root entry out of sync with package.json** The root `""` entry in `package-lock.json` still records `"@usearete/sdk": "^0.0.1"`, but `package.json` was updated to `"^0.1.4"`. npm v7+ regenerates the lock file's root package section from `package.json`, so the next `npm install` on a clean tree would write `^0.1.4` there automatically — but shipping an already-desynchronised lock file can confuse tooling that diffs or audits the two files. This looks like the lock file wasn't regenerated after `package.json` was edited. How can I resolve this? If you propose a fix, please make it concise.

github-actions · 2026-06-17T22:04:04Z

🤖 Created releases:

🌻

github-actions Bot added the autorelease: pending label May 31, 2026

vercel Bot deployed to Preview May 31, 2026 16:34 View deployment

greptile-apps Bot reviewed May 31, 2026

View reviewed changes

github-actions Bot force-pushed the release-please--branches--main branch from 3aa7be1 to c9d48ac Compare June 1, 2026 01:16

vercel Bot deployed to Preview June 1, 2026 01:16 View deployment

chore: release main

60289f4

github-actions Bot force-pushed the release-please--branches--main branch from c9d48ac to 60289f4 Compare June 17, 2026 21:53

vercel Bot deployed to Preview June 17, 2026 21:54 View deployment

adiman9 merged commit 4f3fc39 into main Jun 17, 2026
11 checks passed

adiman9 deleted the release-please--branches--main branch June 17, 2026 22:03

github-actions Bot added autorelease: tagged and removed autorelease: pending labels Jun 17, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore: release main#112

chore: release main#112
adiman9 merged 1 commit into
mainfrom
release-please--branches--main

github-actions Bot commented May 31, 2026 •

edited

Loading

Uh oh!

vercel Bot commented May 31, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot commented May 31, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot May 31, 2026

Uh oh!

greptile-apps Bot May 31, 2026

Uh oh!

greptile-apps Bot May 31, 2026

Uh oh!

Uh oh!

github-actions Bot commented Jun 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

	arete-sdk = { package = "arete-a4-sdk", version = "0.1.3", path = "../rust/arete-a4-sdk", optional = true }
	arete-sdk = { package = "arete-a4-sdk", version = "0.1.4", path = "../rust/arete-a4-sdk", optional = true }

Uh oh!

Conversation

github-actions Bot commented May 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🤖 I have created a release beep boop

0.0.2 (2026-06-17)

Features

Bug Fixes

0.1.4 (2026-06-17)

Miscellaneous Chores

Dependencies

0.1.4 (2026-06-17)

Miscellaneous Chores

Dependencies

0.1.4 (2026-06-17)

Features

0.1.4 (2026-06-17)

Features

Bug Fixes

Dependencies

0.1.4 (2026-06-17)

Features

Bug Fixes

Dependencies

0.1.4 (2026-06-17)

Miscellaneous Chores

0.1.4 (2026-06-17)

Miscellaneous Chores

Dependencies

0.1.4 (2026-06-17)

Bug Fixes

0.1.4 (2026-06-17)

Bug Fixes

0.1.4 (2026-06-17)

Bug Fixes

Dependencies

0.1.4 (2026-06-17)

Bug Fixes

Uh oh!

vercel Bot commented May 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

greptile-apps Bot commented May 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 4/5

Important Files Changed

Uh oh!

greptile-apps Bot May 31, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot May 31, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot May 31, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions Bot commented Jun 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

github-actions Bot commented May 31, 2026 •

edited

Loading

vercel Bot commented May 31, 2026 •

edited

Loading

greptile-apps Bot commented May 31, 2026 •

edited

Loading