Skip to content

chore: add changeset for v1.3.0#952

Merged
TabishB merged 3 commits intomainfrom
changeset-v1.3.0
Apr 11, 2026
Merged

chore: add changeset for v1.3.0#952
TabishB merged 3 commits intomainfrom
changeset-v1.3.0

Conversation

@TabishB
Copy link
Copy Markdown
Contributor

@TabishB TabishB commented Apr 11, 2026

Summary

Adds a changeset for the next release, covering all user-facing changes since v1.2.0:

New Features

Bug Fixes

Skipped (docs/CI/test only)


Closes the previous changeset PR #774 which was stale.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • New Features

    • Added support for JetBrains Junie tools and command generation
    • Added Lingma IDE configuration support
    • Added ForgeCode and IBM Bob coding-assistant tool support
  • Bug Fixes

    • Made shell completion installation opt-in to avoid PowerShell encoding corruption
    • Prevented false GitHub Copilot detection when only a bare directory exists
    • Fixed command-generation issues (pi.dev) related to reference transforms and template arguments

@1code-async
Copy link
Copy Markdown
Contributor

1code-async bot commented Apr 11, 2026

🤖 Automation triggered: PR Reviews

I'm starting to work on this automatically.


View live progress

Powered by 1Code

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 11, 2026

📝 Walkthrough

Walkthrough

A new changeset file is added for @fission-ai/openspec documenting a minor release that adds tool/command generation support for JetBrains Junie, Lingma IDE, ForgeCode, and IBM Bob, and records bug fixes for shell completion opt-in, GitHub Copilot false detection, and pi.dev command generation fixes.

Changes

Cohort / File(s) Summary
Changeset Documentation
/.changeset/new-tools-and-fixes.md
Adds a changeset entry documenting a minor version bump for @fission-ai/openspec, listing new tool support (JetBrains Junie, Lingma IDE, ForgeCode, IBM Bob) and bug fixes (PowerShell shell-completion opt-in, false GitHub Copilot detection, pi.dev command generation fixes).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

🐰 I hopped through changelogs bright,

Junie, Lingma, ForgeCode in sight,
Completions now ask before they run,
Copilot false alarms undone,
Pi commands fixed—now that's fun! 🎉

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'chore: add changeset for v1.3.0' is vague and generic, using a non-descriptive pattern that doesn't convey what actual changes or improvements are included in v1.3.0. Consider a more descriptive title like 'chore: add v1.3.0 changeset (Junie, Lingma IDE, ForgeCode support)' to better communicate the key features and fixes being released.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch changeset-v1.3.0

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
.changeset/new-tools-and-fixes.md (1)

7-16: Consider adding PR references for each bullet for changelog traceability.

Adding issue/PR numbers in-line improves auditability for release consumers and maintainers.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.changeset/new-tools-and-fixes.md around lines 7 - 16, The changelog entries
(e.g., "Junie support", "Lingma IDE support", "ForgeCode support", "IBM Bob
support", "Shell completions opt-in", "Copilot auto-detection", "pi.dev command
generation") need inline PR/issue references for traceability; update each
bullet to append a concise reference like "(`#1234`)" or "(GH-1234)" pointing to
the merged PR or issue, ensuring consistent formatting across all bullets and
keeping the existing wording intact so reviewers can trace each change back to
its PR/issue.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.changeset/new-tools-and-fixes.md:
- Around line 12-16: Update the Bug Fixes section in the changeset to include
the two missing user-facing fixes: add a bullet describing the plural "commands/
directory convention" fix (mentioning the plural 'commands/' directory) and add
a bullet describing the "openspec status" command now gracefully exiting when no
changes exist (reference the openspec status command). Ensure both bullets
follow the existing style (short title — brief description) and are placed
alongside the other Bug Fixes entries so the v1.3.0 release notes reflect these
fixes.

---

Nitpick comments:
In @.changeset/new-tools-and-fixes.md:
- Around line 7-16: The changelog entries (e.g., "Junie support", "Lingma IDE
support", "ForgeCode support", "IBM Bob support", "Shell completions opt-in",
"Copilot auto-detection", "pi.dev command generation") need inline PR/issue
references for traceability; update each bullet to append a concise reference
like "(`#1234`)" or "(GH-1234)" pointing to the merged PR or issue, ensuring
consistent formatting across all bullets and keeping the existing wording intact
so reviewers can trace each change back to its PR/issue.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 26a488c9-09bd-460a-b360-aace95051133

📥 Commits

Reviewing files that changed from the base of the PR and between 3424825 and 1b2681b.

📒 Files selected for processing (1)
  • .changeset/new-tools-and-fixes.md

Comment on lines +12 to +16
### Bug Fixes

- **Shell completions opt-in** — Completion install is now opt-in, fixing PowerShell encoding corruption
- **Copilot auto-detection** — Prevented false GitHub Copilot detection from a bare `.github/` directory
- **pi.dev command generation** — Fixed command reference transforms and template argument passing
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Bug-fix section is missing two user-facing fixes from this release scope.

Based on the PR objectives, the changeset should also include:

  • plural commands/ directory convention fix
  • openspec status graceful exit when no changes exist

Without these, the v1.3.0 release notes are incomplete.

Suggested patch
 ### Bug Fixes
 
 - **Shell completions opt-in** — Completion install is now opt-in, fixing PowerShell encoding corruption
 - **Copilot auto-detection** — Prevented false GitHub Copilot detection from a bare `.github/` directory
+- **commands/ directory naming** — Switched to plural `commands/` to match OpenCode convention
+- **`openspec status` empty state** — Command now exits gracefully when no changes exist
 - **pi.dev command generation** — Fixed command reference transforms and template argument passing
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Bug Fixes
- **Shell completions opt-in** — Completion install is now opt-in, fixing PowerShell encoding corruption
- **Copilot auto-detection** — Prevented false GitHub Copilot detection from a bare `.github/` directory
- **pi.dev command generation** — Fixed command reference transforms and template argument passing
### Bug Fixes
- **Shell completions opt-in** — Completion install is now opt-in, fixing PowerShell encoding corruption
- **Copilot auto-detection** — Prevented false GitHub Copilot detection from a bare `.github/` directory
- **commands/ directory naming** — Switched to plural `commands/` to match OpenCode convention
- **`openspec status` empty state** — Command now exits gracefully when no changes exist
- **pi.dev command generation** — Fixed command reference transforms and template argument passing
🧰 Tools
🪛 LanguageTool

[uncategorized] ~15-~15: The official name of this software platform is spelled with a capital “H”.
Context: ...se GitHub Copilot detection from a bare .github/ directory - **pi.dev command generati...

(GITHUB)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.changeset/new-tools-and-fixes.md around lines 12 - 16, Update the Bug Fixes
section in the changeset to include the two missing user-facing fixes: add a
bullet describing the plural "commands/ directory convention" fix (mentioning
the plural 'commands/' directory) and add a bullet describing the "openspec
status" command now gracefully exiting when no changes exist (reference the
openspec status command). Ensure both bullets follow the existing style (short
title — brief description) and are placed alongside the other Bug Fixes entries
so the v1.3.0 release notes reflect these fixes.

Copy link
Copy Markdown
Collaborator

@alfred-openspec alfred-openspec left a comment

Choose a reason for hiding this comment

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

Nice catch-up changeset overall, but I'm not comfortable approving this as-is because the file doesn't yet match the stated scope.

The PR summary says this covers all user-facing changes since v1.2.0, but the changeset is still missing at least these two user-facing bug fixes that are already mentioned elsewhere in the PR context:

  • #760, OpenCode uses plural commands/ directory
  • #759, openspec status exits gracefully when no changes exist

Once those are reflected in the changeset, this looks good to approve.

Copy link
Copy Markdown
Collaborator

@alfred-openspec alfred-openspec left a comment

Choose a reason for hiding this comment

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

Checked the existing .changeset files and you were right: those two fixes are already covered by committed changesets (fix-opencode-commands-directory.md and graceful-status-no-changes.md).

Given that, this PR looks good to me. Approving.

@TabishB TabishB added this pull request to the merge queue Apr 11, 2026
Merged via the queue into main with commit cce787e Apr 11, 2026
9 checks passed
@TabishB TabishB deleted the changeset-v1.3.0 branch April 11, 2026 15:41
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