Skip to content

Bump current version of soroban-env to latest tip - #901

Closed
github-actions[bot] wants to merge 1 commit into
protocol-nextfrom
automation/bump-soroban-env
Closed

Bump current version of soroban-env to latest tip#901
github-actions[bot] wants to merge 1 commit into
protocol-nextfrom
automation/bump-soroban-env

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated update for the soroban-env dependency on protocol-next.

@github-actions
github-actions Bot force-pushed the automation/bump-soroban-env branch 4 times, most recently from 8f832a7 to 2255feb Compare July 30, 2026 12:52
@github-actions
github-actions Bot force-pushed the automation/bump-soroban-env branch from 2255feb to 0fe0bf3 Compare July 31, 2026 00:56
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedcargo/​stellar-xdr@​28.0.093100100100100

View full report

@Shaptic

Shaptic commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Closing ahead of the Protocol 28 GA flip: this automation PR pins soroban-env-host-curr to a git rev, which the GA flip replaces with the crates.io =28.0.0 release, and the update script's Cargo.toml rewrite conflicts with the hand-tuned manifest. Tracking: stellar/go-stellar-sdk#5967. The cron will regenerate against the re-synced protocol-next after the train.

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.

1 participant