fix(deps): update dependency @fission-ai/openspec to v1.4.0 #213
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!213
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/213/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.3.1→1.4.0Release Notes
Fission-AI/OpenSpec (@fission-ai/openspec)
v1.4.0Compare Source
Minor Changes
#1003
342ed43Thanks @Miss-you! - ### New Features.kimi/skills/Other
Added Kimi-specific docs and init coverage aligned with skill-based
/skill:openspec-*usage#1154
aa16080Thanks @TabishB! - ### New Features.vibe/skills/Bug Fixes
compinitOther
Clearer validation hints — When a requirement has SHALL/MUST only in its header,
openspec validatenow points you to move the keyword onto the requirement body line instead of showing the generic error#1030
485c97eThanks @TabishB! - ### New Features/opsx:syncskills and commands by default.Patch Changes
#1111
7fdb177Thanks @TabishB! - ### FixedConfiguration
📅 Schedule: (UTC)
* * * * *)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
op1st Pipelines as Code/forgejo-mcp-on-pull-request-h6th4 is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-h6th4 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-h6th4 -fop1st Pipelines as Code/forgejo-mcp-code-scans-8ckb7 is running.
Starting Pipelinerun forgejo-mcp-code-scans-8ckb7 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-8ckb7 -fop1st Pipelines as Code/forgejo-mcp-code-scans-8ckb7 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-h6th4 has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-fxbrc is running.
Starting Pipelinerun forgejo-mcp-code-scans-fxbrc in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-fxbrc -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-vk6k7 is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-vk6k7 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-vk6k7 -fop1st Pipelines as Code/forgejo-mcp-code-scans-fxbrc has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-vk6k7 has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-6jnpg is running.
Starting Pipelinerun forgejo-mcp-code-scans-6jnpg in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-6jnpg -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-ssgcc is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-ssgcc in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-ssgcc -fop1st Pipelines as Code/forgejo-mcp-code-scans-6jnpg has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-ssgcc has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check