Add Foundry publish workflow + versioned tags

[anand-testcompare]

This adds a dedicated publish-foundry workflow (modeled after palantir-compute-module-pipeline-search) and moves Foundry pushing out of the combined publish workflow.

• Foundry pushes now use incrementing semver tags (e.g. 0.1.3) only.
• release-version dispatches both GHCR publish + Foundry publish on the release tag.
• On PRs, publish-foundry builds + validates (no push), so Foundry-specific checks are visible in Actions.

Summary by CodeRabbit

Release Notes

• New Features

  • Added new publishing workflow featuring multi-platform Docker builds, OpenAPI artifact generation and validation, plus automated runtime health checks to ensure deployment reliability.

• Chores

  • Refactored platform image publishing workflow to consolidate and simplify deployment to GHCR registry.
  • Enhanced release version workflow to orchestrate multiple concurrent publishing destinations.
  • Updated workflow and configuration documentation references.

[railway-app]

🚅 Deployed to the dspy-reference-examples-pr-16 environment in dspy-reference-example

Service	Status	Web	Updated (UTC)
dspy-reference-examples	✅ Success (View Logs)	Web	Feb 14, 2026 at 3:36 am

[coderabbitai]

Walkthrough

Introduces a dedicated Foundry publishing workflow, removes Foundry logic from the platform images workflow, updates release version workflow to trigger both publishing workflows, and adds documentation reference.

Changes

Cohort / File(s)	Summary
New Foundry Publishing Workflow .github/workflows/publish-foundry.yml	New GitHub Actions workflow that builds and publishes Docker images to Foundry registry, triggered on PRs (specific paths), version tags, and manual dispatch. Includes OpenAPI validation, Docker Buildx setup, conditional push/load logic, metadata resolution, Foundry registry authentication, and health endpoint smoke tests.
Workflow Refactoring .github/workflows/publish-platform-images.yml, .github/workflows/release-version.yml, .env.example	Removes Foundry-related publishing logic from platform images workflow; consolidates to GHCR-only publishing with simplified tag generation. Release version workflow updated to dispatch both publish-foundry and publish-platform-images workflows. Documentation comment added referencing Foundry workflow.

Poem

🐇 A rabbit hops with glee today,

Two workflows now go separate ways,

Foundry builds its own sweet nest,

While platforms get some well-earned rest,

Cleaner code hops into place—*thump thump* success!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately captures the main objectives: introducing a new Foundry publish workflow and implementing versioned tagging for releases.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/publish-foundry-versioned-tags

---

No actionable comments were generated in the recent review. 🎉

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}