Skip to content

Release 1.0.0#180

Merged
prim-8 merged 2 commits into
mainfrom
release-1.0.0
Jun 1, 2026
Merged

Release 1.0.0#180
prim-8 merged 2 commits into
mainfrom
release-1.0.0

Conversation

@etbyrd
Copy link
Copy Markdown
Member

@etbyrd etbyrd commented Jun 1, 2026

Summary

Coordinated lockstep version bump across the four SDKs and the scaffold version ranges:

  • cli-node/package.json: 0.38.0 -> 1.0.0 (triggers CLI Release workflow on merge)
  • sdk-node/package.json: 0.38.0 -> 1.0.0 (triggers Node Release workflow on merge)
  • sdk-python/pyproject.toml: 0.38.0 -> 1.0.0 (triggers Python Release workflow on merge)
  • sdk-go/VERSION: 0.38.0 -> 1.0.0 (triggers Go Release workflow on merge)
  • cli-node/src/oclif/function-templates.ts: SDK_VERSION_RANGE and CLI_VERSION_RANGE -> ^1.0.0. Required by the lockstep test in functions-init.test.ts.

Test plan

  • pnpm lint clean
  • pnpm typecheck clean
  • pnpm test 517/517 green
  • After merge, watch all four release workflows succeed on main
  • npm view @primitivedotdev/cli version returns 1.0.0
  • npm view @primitivedotdev/sdk version returns 1.0.0
  • pip index versions primitivedotdev shows 1.0.0
  • Brew tap auto-bumps to 1.0.0 cleanly
  • primitive functions init <name> scaffolds with ^1.0.0 ranges in the generated package.json

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Jun 1, 2026

Greptile Summary

Coordinated lockstep version bump from 0.38.0 to 1.0.0 across all four SDKs (Node, Python, Go, CLI) and the scaffold version ranges in function-templates.ts.

  • sdk-node/package.json, sdk-python/pyproject.toml, and sdk-go/VERSION each receive the 1.0.0 version string, triggering their respective release workflows on merge.
  • cli-node/package.json is likewise bumped to 1.0.0, and CLI_VERSION_RANGE / SDK_VERSION_RANGE in function-templates.ts are updated to ^1.0.0 so that primitive functions init scaffolds new projects pointing at the correct major version range.

Confidence Score: 5/5

All changes are mechanical version string updates with no logic, algorithm, or API contract changes — safe to merge.

Every changed line is a version string or version range constant. The scaffold ranges in function-templates.ts are kept in lockstep with the new major, which matches the invariant the functions-init.test.ts lockstep test enforces. No behavioural code is touched.

No files require special attention.

Important Files Changed

Filename Overview
cli-node/package.json Version bumped from 0.38.0 to 1.0.0 for the 1.0 release.
cli-node/src/oclif/function-templates.ts SDK_VERSION_RANGE and CLI_VERSION_RANGE updated from ^0.38.0 to ^1.0.0 to match the new major release, keeping scaffolded projects in sync.
sdk-go/VERSION Go SDK VERSION file bumped from 0.38.0 to 1.0.0.
sdk-node/package.json Node SDK version bumped from 0.38.0 to 1.0.0.
sdk-python/pyproject.toml Python SDK version bumped from 0.38.0 to 1.0.0 in pyproject.toml.

Reviews (3): Last reviewed commit: "Merge main into release-1.0.0 (pulls in ..." | Re-trigger Greptile

Lockstep version bump across cli-node, sdk-node, sdk-python, sdk-go, and the function-templates scaffold ranges from 0.38.0 to 1.0.0.
@prim-8 prim-8 added this pull request to the merge queue Jun 1, 2026
Merged via the queue into main with commit 3d44983 Jun 1, 2026
12 checks passed
@prim-8 prim-8 deleted the release-1.0.0 branch June 1, 2026 18:29
@prim-8 prim-8 mentioned this pull request Jun 1, 2026
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