Skip to content

Remove explicit pnpm version from workflows to fix version conflict - #7

Merged
huangyiirene merged 2 commits into
mainfrom
copilot/update-action-workflow-file
Jan 18, 2026
Merged

Remove explicit pnpm version from workflows to fix version conflict#7
huangyiirene merged 2 commits into
mainfrom
copilot/update-action-workflow-file

Conversation

CopilotAI commented Jan 18, 2026

Copy link
Copy Markdown
Contributor

The CI workflow failed because pnpm/action-setup@v4 detected conflicting versions: version: 10 in the workflow config vs "packageManager": "pnpm@10.28.0" in package.json.

Changes

  • Removed version: 10 from pnpm/action-setup@v4 in both CI and release workflows
  • The action now uses the version specified in package.json's packageManager field (10.28.0)
# Before
- name: Install pnpmuses: pnpm/action-setup@v4with:
version: 10# After
- name: Install pnpmuses: pnpm/action-setup@v4

Reference: https://github.com/objectstack-ai/spec/actions/runs/21110164385/job/60707559636#step:4:1

Original prompt

引用: https://github.com/objectstack-ai/spec/actions/runs/21110164385/job/60707559636#step:4:1


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: huangyiirene <7665279+huangyiirene@users.noreply.github.com>
CopilotAI changed the title [WIP] Update action workflow file for improvementsRemove explicit pnpm version from workflows to fix version conflictJan 18, 2026
@huangyiirene
huangyiirene marked this pull request as ready for review January 18, 2026 10:56
@huangyiirene
huangyiirene merged commit de36919 into mainJan 18, 2026
1 check passed
xuyushun441-sys added a commit that referenced this pull request Jun 3, 2026
…d read-only permission allowlist (#1555)
AGENTS.md:
- Drop the stale ".github/copilot-instructions.md mirror" instruction — that
file doesn't exist, and Copilot (coding agent + CLI, since Aug 2025) reads
AGENTS.md natively. Single source of truth for all agents.
- Multi-agent discipline: prefer one git worktree per agent/task for physical
isolation; frame the defensive rules as the shared-working-tree fallback.
- Add rule #7: merge only after remote CI is green, never `gh pr merge --auto`
(#1475 — auto-merge can land a red PR on shared main).
.claude/settings.json (new, committed/shared):
- Read-only permission allowlist derived from recent transcript usage, so
parallel agents prompt less. Browser/preview observation tools
(screenshot/snapshot/logs/network/list) + `agent-browser snapshot|skills`.
- Deliberately excludes mutating/arbitrary-exec calls (preview_eval, click,
fill, start/stop, pnpm, node, npx) and anything Claude Code already
auto-allows (git/gh read-only, grep, cat, ls, …).
Co-authored-by: Jack Zhuang <277994282+os-zhuang@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
xuyushun441-sys added a commit that referenced this pull request Jun 13, 2026
#1821)
Small models (e.g. claude-haiku) sometimes answered a "draw a bar chart"
request with a markdown TABLE — running query_data/aggregate_data and
formatting the numbers — instead of calling visualize_data. This was a
tool-selection problem, not a capability gap: the chart preference was buried
as guideline #7 and competed with guideline #4 ("format with markdown
tables").
- data-explorer-skill.ts: add a prominent "Choosing the right tool" section
ABOVE the guidelines — chart intent (incl. CN terms 图表/柱状图/折线图/饼图/画图)
→ MUST call visualize_data; never substitute a table; reconcile the
table-formatting guideline; fix duplicate guideline numbering.
- visualize-data.tool.ts: strengthen the tool description to be imperative
("the ONLY tool that draws a chart… you MUST call this, not a table; if you
already fetched the numbers, still call visualize_data to render them").
Prompt-only tuning — no behavior/contract change. Raises the likelihood the
model reaches for visualize_data on a plain chart request without an explicit
"use visualize_data" nudge.
Co-authored-by: Jack Zhuang <277994282+os-zhuang@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
os-zhuang added a commit that referenced this pull request Jun 28, 2026
…ta-protocol name; no rename) (#2431)
Per maintainer decision: keep the already-published `@objectstack/metadata-protocol`
package name. Renaming churns downstream for ~0 benefit. The `protocol` suffix is a
deliberate, low-cost naming exception — the real contract lives in
`@objectstack/spec/api`, not the impl package.
- D10: replace the "rename → metadata-runtime" clause with "name retained; content
converges to the metadata-management impl".
- Open Question #7: resolved (keep the name; README note to clarify impl-vs-contract).
- Status: rev.8; notes D9 step-1 (interface segmentation) shipped in #2429.
Docs only; empty changeset.
Co-authored-by: Jack Zhuang <277994282+os-zhuang@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
os-zhuang added a commit that referenced this pull request Jul 27, 2026
…ions (#3563 PR-2) (#3571)
Closes the largest gap in the #3563 route audit: the whole /actions domain —
the documented way to expose custom server-side operations
(engine.registerAction) — had no SDK expression at all, so every console
hand-rolled fetch for it.
- client.actions.invoke(object, action, { recordId, params }) — POST
/api/v1/actions/:object/:action. recordId travels in the body, which both
server URL shapes honor. The path is fixed (not discovery-routed): actions
is not in ApiRoutesSchema, same precedent as projects' /api/v1/cloud.
- client.actions.invokeGlobal(action, opts) — the wildcard
/actions/global/:action shape.
- The handler's own business failure surfaces as { success:false, error }
(the dispatcher's inner envelope), deliberately not thrown, so callers can
toast it. Unit tests cover URL shape, encoding, body defaults, the global
variant, and the inner-failure path.
Ledger: all three /actions rows flip to sdk; the gap ratchet drops 27 → 24 —
first real exercise of the PR-1 guard.
Documentation stops lying (audit findings):
- client README: the six phantom methods are gone (meta.getObject,
views.share, views.setDefault, workflow.approve/reject, ai.chat — replaced
with the real calls where one exists), and the hand-written "all 13
namespaces / FULLY COMPLIANT" claims now defer to the CI-enforced ledger.
- CLIENT_SPEC_COMPLIANCE.md: retired to a tombstone. Its verdict was measured
against DEFAULT_DISPATCHER_ROUTES — a table nothing in runtime consumes,
missing five of the domains it should have been measuring.
- content/docs/api/client-sdk.mdx: documents the new actions surface;
the automation row now reflects the real method count.
Pre-existing, untouched: the bare `tsc -p` TS2741 (routeMap missing graphql)
reproduces identically on main — its root is the stale graphql entry in
ApiRoutesSchema, tracked as audit follow-up #7 (spec-major territory).
Verified: client 122 passed (5 new), runtime 653 passed, both ledger guard
halves green, eslint clean.
Claude-Session: https://claude.ai/code/session_01LX9ut3MK3KykE11S9bJmv5
Co-authored-by: Claude <noreply@anthropic.com>
Sign up for freeto 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

@huangyiirene