Skip to content

Conversation

@github-actions
Copy link

API Version: 1.96

This PR was automatically generated by the API docs workflow.

What's included

  • ✅ New base spec copied from Platform repo
  • ✅ Comparison overlay generated
  • ✅ Changes analyzed and categorized
  • ✅ Claude-generated overlay files (requires review)

Next steps

  1. Review Claude-generated overlays in claude-generated-overlays.md
  2. Extract overlay files from the markdown into separate YAML files
  3. Edit overlays for accuracy and completeness
  4. Run validation: python scripts/validate_overlay.py <file>
  5. Request engineering review from appropriate team
  6. Once approved, add label overlays-approved to trigger Phase 3

Analysis Summary

See analysis JSON file for detailed breakdown of changes.


Triggered by: llewellyn-sl
Platform commit: manual trigger

bebosudo and others added 3 commits January 2, 2026 11:02
* Add helm to v25.3 sidebar

* Bump helm chart version to 0.20.1
* Add all available seqera compute regions to Platform Cloud docs

* Expand SA into South Africa

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com>

---------

Signed-off-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Add phase 2 automation workflows

* Add claude-generated-overlays.md to YAML extraction

* Update apply-overlays-and-regenerate.yml
@llewellyn-sl llewellyn-sl self-assigned this Jan 5, 2026
@llewellyn-sl llewellyn-sl self-requested a review January 5, 2026 09:28
@llewellyn-sl llewellyn-sl added the overlays-approved API docs automation: Overlay approval label to trigger docs regeneration label Jan 5, 2026
@llewellyn-sl llewellyn-sl removed the overlays-approved API docs automation: Overlay approval label to trigger docs regeneration label Jan 5, 2026
llewellyn-sl and others added 7 commits January 5, 2026 17:31
Add critical guidance on using remove-then-update pattern when replacing
arrays (enums, required fields) in OpenAPI overlays. Direct update actions
append to existing arrays instead of replacing them, creating invalid YAML
with duplicate values.

Documentation changes:
- Add "Array Replacement Pattern" section to overlay-patterns.md with
  detailed examples of the problem and solution
- Add troubleshooting guidance to platform-api-docs/README.md
- Include examples for fixing duplicate required fields and enums
- Add workflow progress log (claude-progress.md)

Spec improvements:
- Apply schema deduplication overlay to decorated spec
- Fix 12 validate-json-schema errors (duplicate items in required arrays)
- Archive schema-required-duplicates-overlay-1.96.yaml
- Replace seqera-api-latest-decorated.yml with deduplicated .yaml version

Cleanup:
- Remove intermediate backup files
- Remove unused data-links path params overlay (API design issue)
- Keep only clean deduplicated decorated spec

The decorated spec now passes all schema validation checks except for
the 4 known path-params errors requiring backend API fixes.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
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.

3 participants