Skip to content

Bump version to v0.2.0#55

Merged
chrismaz11 merged 2 commits intomasterfrom
copilot/update-to-v020
Mar 18, 2026
Merged

Bump version to v0.2.0#55
chrismaz11 merged 2 commits intomasterfrom
copilot/update-to-v020

Conversation

Copy link
Contributor

Copilot AI commented Mar 17, 2026

Project was still pinned at 0.1.0 across all package manifests. This bumps every workspace to 0.2.0 and records the release in the changelog.

Summary

  • package.json (root), sdk/package.json, apps/api/package.json, apps/web/package.json, packages/core/package.json, packages/contracts/package.jsonversion field: 0.1.00.2.0
  • apps/api/package-lock.json — top-level and packages[""] version entries updated to match
  • CHANGELOG.md — new 0.2.0 section added with today's date

AI Disclosure (optional)

  • AI-assisted changes are included in this PR

Review Checklist

  • Human review requested
  • Tests added or updated where appropriate
  • No secrets, tokens, cookies, or raw PII were added to code, logs, fixtures, or docs
  • Security impact and remaining risks are described

Version metadata change only. No logic, auth, storage, or security surfaces touched. No risk introduced.


📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

@vercel
Copy link

vercel bot commented Mar 17, 2026

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

Project Deployment Actions Updated (UTC)
api Ready Ready Preview, Comment Mar 17, 2026 10:54pm
trustsignal Ready Ready Preview, Comment Mar 17, 2026 10:54pm

Co-authored-by: chrismaz11 <24700273+chrismaz11@users.noreply.github.com>
Copilot AI changed the title [WIP] Update version to v0.2.0 Bump version to v0.2.0 Mar 17, 2026
Copilot AI requested a review from chrismaz11 March 17, 2026 22:55
@chrismaz11 chrismaz11 marked this pull request as ready for review March 18, 2026 02:22
Copilot AI review requested due to automatic review settings March 18, 2026 02:22
@chrismaz11 chrismaz11 merged commit 5e384e2 into master Mar 18, 2026
17 checks passed
@chrismaz11 chrismaz11 deleted the copilot/update-to-v020 branch March 18, 2026 02:23
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Bumps the repository’s package versions from 0.1.0 to 0.2.0 across the main workspaces (and sdk/), and adds a corresponding 0.2.0 entry to the changelog.

Changes:

  • Update version to 0.2.0 in root + workspace package.json files and sdk/package.json.
  • Update apps/api/package-lock.json top-level/package-root version fields.
  • Add a 0.2.0 section to CHANGELOG.md.

Reviewed changes

Copilot reviewed 7 out of 8 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
package.json Bumps root package version to 0.2.0.
sdk/package.json Bumps SDK package version to 0.2.0.
apps/api/package.json Bumps API workspace version to 0.2.0.
apps/api/package-lock.json Updates API lockfile version metadata (partially).
apps/web/package.json Bumps web workspace version to 0.2.0.
packages/core/package.json Bumps core workspace version to 0.2.0.
packages/contracts/package.json Bumps contracts workspace version to 0.2.0.
CHANGELOG.md Records the 0.2.0 version bump entry.
Files not reviewed (1)
  • apps/api/package-lock.json: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 3 to 7
"private": true,
"version": "0.1.0",
"version": "0.2.0",
"type": "commonjs",
"engines": {
"node": "20.x"
Comment on lines +7 to +8
## 0.2.0 - 2026-03-17


### Changed

- Bumped all package versions from `0.1.0` to `0.2.0` (`package.json`, `sdk/package.json`, `apps/api/package.json`, `apps/web/package.json`, `packages/core/package.json`, `packages/contracts/package.json`).
Comment on lines 1 to 12
{
"name": "@deed-shield/api",
"version": "0.1.0",
"version": "0.2.0",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "@deed-shield/api",
"version": "0.1.0",
"version": "0.2.0",
"hasInstallScript": true,
"dependencies": {
"@deed-shield/core": "file:../../packages/core",
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e3d5319e4f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

"name": "deed-shield",
"private": true,
"version": "0.1.0",
"version": "0.2.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update root lockfile for the 0.2.0 version bump

Bumping the root manifest to 0.2.0 here without also updating package-lock.json leaves the lock metadata for the root/workspace packages at 0.1.0, which creates immediate lockfile drift for root install/verification workflows and undermines deterministic CI evidence for this release-only change. Regenerate and commit the root lockfile together with this version change.

Useful? React with 👍 / 👎.

{
"name": "@deed-shield/api",
"version": "0.1.0",
"version": "0.2.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Regenerate API lockfile after core version change

This lockfile edit only bumps the top-level API version, but apps/api/package-lock.json still contains @deed-shield/core as 0.1.0 under the ../../packages/core entry while packages/core/package.json was changed to 0.2.0. That internal inconsistency causes avoidable lockfile churn in apps/api installs and weakens reproducibility of the workspace release state.

Useful? React with 👍 / 👎.

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.

3 participants