Skip to content

🔖 chore: bump version to 0.3.18#109

Closed
vish-dini wants to merge 1 commit into
mainfrom
release/v0.3.18
Closed

🔖 chore: bump version to 0.3.18#109
vish-dini wants to merge 1 commit into
mainfrom
release/v0.3.18

Conversation

@vish-dini
Copy link
Copy Markdown
Collaborator

Release version bump for v0.3.18.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the version of the inboxapi-cli package from 0.3.14 to 0.3.18 across Cargo.toml, Cargo.lock, and package.json. I have no feedback to provide.

@vish-dini vish-dini requested a review from shaond May 12, 2026 00:12
@sara-dini
Copy link
Copy Markdown
Collaborator

Status sweep (2026-05-13):

  • Release + CI checks are green.
  • No unresolved review threads.
  • Merge is blocked only by outstanding requested review from @shaond.

Next concrete step:

@sara-dini
Copy link
Copy Markdown
Collaborator

Status sweep (2026-05-15 UTC):

  • Rechecked PR 🔖 chore: bump version to 0.3.18 #109 gate/check state.
  • CI and release checks remain green on-head.
  • No unresolved review threads or requested code changes detected.
  • Merge remains blocked by outstanding requested review from @shaond.

Next concrete step:

@vish-dini
Copy link
Copy Markdown
Collaborator Author

Blocking note from audit:

v0.3.18 was already tagged and published from commit 2b76608, but main has moved since then (most recently #111 merged on 2026-05-15). Merging this PR as-is would set trunk version metadata to 0.3.18 even though the published v0.3.18 artifacts do not contain current main code.

Recommended next step:

  • do not merge this stale version-bump PR as-is
  • either backport current trunk fixes into a fresh 0.3.18 rebuild, or more likely cut a new version from current main
  • close/recreate the release PR so version metadata matches the code actually shipped

Separate baseline issue still open: #106 (no-arg MCP schemas omit properties, breaking OpenAI/Codex tool ingestion).

@sara-dini
Copy link
Copy Markdown
Collaborator

Status delta (2026-05-15 UTC): addressed the baseline blocker from the audit note.

Recommended next concrete step for this stale release PR:

  1. Do not merge 🔖 chore: bump version to 0.3.18 #109 as-is.
  2. Land fix(mcp): normalize no-arg tool schemas for OpenAI compatibility #112 on main.
  3. Cut a fresh version-bump/release PR from updated main (instead of reusing stale v0.3.18 metadata).

@sara-dini
Copy link
Copy Markdown
Collaborator

Closing as stale to prevent shipping mismatched release metadata: v0.3.18 artifacts were already published from an older commit, and #112 has since merged to main. Next step: cut a fresh version-bump/release PR from current main.

@sara-dini sara-dini closed this May 16, 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