You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bundle.fetch(): the default ref 'stable' doesn't exist yet #21
GET /repos/MarketSquare/robotframework-plugins/commits/stable returns HTTP 422 ("No commit found for SHA: stable"). The branch latest exists and points at the same commit as main (56547f0, 2026-11-16).
Purpose
RELEASING.md says release.yml moves the stable and latest branches when a plugin is released (<plugin>--v<version>). No plugin tag exists yet, only robotframework-plugins-v2026.11.0.dev1 and the older v* / rf-agentskills-v* tags, so stable has never been created. The README also tells marketplace users to "use stable for the latest release".
rf-mcp is going to offer the official skills from a ref as an opt-in, next to the content bundled in the wheel: RF_MCP_OFFICIAL_SKILLS=stable | latest | <tag> | <sha>, with the wheel as the offline fallback. stable is the channel it will recommend, because it holds released, reviewed content. Today, choosing it silently falls back to the wheel, and a marketplace pinned to stable cannot be added.
Proposed change
One of:
Create stable now, at the commit of the first content you consider released (for example the commit the 2026.11.0.dev1 wheel was built from, f4e2a26), and let release.yml move it from then on.
Or keep the default but document it: "stable appears with the first <plugin>--v* release; until then use latest or a tag". fetch() could then say so in its error for stable.
Option 1 is what users of the README and of fetch() expect.
Acceptance
bundle.fetch() (default ref) returns a Snapshot, or fails with a message that names the alternative.
The README's "use stable for the latest release" works for a marketplace pin.
Related: #5 (public bundle API, which added fetch()).
Activity