Skip to content

ci(release): publish autograd, nn and optim before the GPU backends #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vyncint merged 1 commit into from
Sep 3, 2026
Merged

ci(release): publish autograd, nn and optim before the GPU backends #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,12 @@ jobs:
set -euo pipefail
version="${TAG#v}"
ua="oxmera-release (github.com/${GITHUB_REPOSITORY})"
crates="oxmera-core oxmera-tensor oxmera-ops oxmera-cpu oxmera-metal oxmera-cuda oxmera-runtime oxmera-autograd oxmera-nn oxmera-optim oxmera oxmera-cli"
# Dependency order INCLUDING versioned dev-dependencies: cargo
# resolves those against the registry at publish time, so a crate
# whose tests depend on oxmera-nn/oxmera-optim (the GPU backends'
# fused-optimizer parity tests) must come after them. 0.3.0's first
# run stopped at oxmera-metal for exactly this reason.
crates="oxmera-core oxmera-tensor oxmera-ops oxmera-cpu oxmera-autograd oxmera-nn oxmera-optim oxmera-metal oxmera-cuda oxmera-runtime oxmera oxmera-cli"

for crate in $crates; do
# Skip versions already on the registry: that is what makes a
Expand Down