-
Notifications
You must be signed in to change notification settings - Fork 5
bug: Version v1.3.4 failed to publish (jumped from v1.3.3 to v1.3.5) #40
Copy link
Copy link
Open
Description
Context
Discord plugin v1.3.4 failed to publish, resulting in a version jump from v1.3.3 directly to v1.3.5.
- Source: Discord discussion (2026-01-03)
- Priority: P1 (from issue-triage assessment)
- Impact: Medium-High (breaks predictable upgrades; may strand users on bad versions)
Evidence
- Discord: "v1.3.4 failed to publish; version jumped from v1.3.3 to v1.3.5"
- Reporter: YogaFlame
- Related: Previous issue Discord Plugin Release Issue: Tags v1.0.0-v1.0.4 are broken #9 (v1.0.x getWavHeader) is different and closed
- Pattern: Indicates release pipeline fragility
Technical Details
- Component: Plugin System / Publishing pipeline (npm, registry, CI workflows)
- Complexity: 3/5 (requires pipeline audit and safeguards)
- Required Expertise: npm publishing, CI release workflows, semver/tagging
Proposed Investigation
- Audit npm error logs + CI run for v1.3.4 publish attempt
- Check for tag creation issues, provenance problems, npm token scope
- Determine if v1.3.4 contained important fixes that users need
- Add automated guard: fail if version already exists / missing changelog
Proposed Prevention
- Add "release checklist" to CI workflow
- Implement dry-run publish in CI before actual release
- Add Slack/Discord notification on publish failure
Acceptance Criteria
- Root cause of v1.3.4 failure documented
- Release workflow improved to prevent recurrence
- Process documented for handling skipped versions
Generated from elizaOS intelligence pipeline
Evidence date: 2026-01-06
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels