Skip to content

Conversation

@tsibley
Copy link
Member

@tsibley tsibley commented Nov 6, 2025

GitHub released public runners.¹ This will ultimately let us use standalone installation archives in our linux/arm64 Docker images.²

Changes to the standalone installer to follow separately³, as those need to be held for merge until after the first release with these builds available.

¹ https://github.blog/changelog/2025-01-16-linux-arm64-hosted-runners-now-available-for-free-in-public-repositories-public-preview/
² nextstrain/docker-base#273
³ #490

Checklist

  • Checks pass
  • Update changelog

tsibley added a commit that referenced this pull request Nov 6, 2025
Conditions on the Nextstrain CLI version being requested, as aarch64
builds¹ will only be available going forward for new releases.  Assumes
the next release will be 10.4.2!

We must wait to merge this until after the first release (i.e. 10.4.2)
of the changes it depends on above.

¹ <#489>
@tsibley tsibley force-pushed the trs/standalone/linux-aarch64 branch from 11e2022 to 777bc92 Compare November 6, 2025 22:55
tsibley added a commit that referenced this pull request Nov 6, 2025
Conditions on the Nextstrain CLI version being requested, as aarch64
builds¹ will only be available going forward for new releases.  Assumes
the next release will be 10.4.2!

We must wait to merge this until after the first release (i.e. 10.4.2)
of the changes it depends on above.

¹ <#489>
tsibley added a commit that referenced this pull request Nov 6, 2025
Conditions on the Nextstrain CLI version being requested, as aarch64
builds¹ will only be available going forward for new releases.  Assumes
the next release will be 10.4.2!

We must wait to merge this until after the first release (i.e. 10.4.2)
of the changes it depends on above.

¹ <#489>
@tsibley tsibley force-pushed the trs/standalone/linux-aarch64 branch from 777bc92 to 543c949 Compare November 6, 2025 23:22
tsibley added a commit that referenced this pull request Nov 7, 2025
Conditions on the Nextstrain CLI version being requested, as aarch64
builds¹ will only be available going forward for new releases.  Assumes
the next release will be 10.4.2!

We must wait to merge this until after the first release (i.e. 10.4.2)
of the changes it depends on above.

¹ <#489>
@tsibley tsibley force-pushed the trs/standalone/linux-aarch64 branch from 543c949 to 412548f Compare November 7, 2025 06:12
tsibley added a commit that referenced this pull request Nov 7, 2025
Conditions on the Nextstrain CLI version being requested, as aarch64
builds¹ will only be available going forward for new releases.  Assumes
the next release will be 10.4.2!

We must wait to merge this until after the first release (i.e. 10.4.2)
of the changes it depends on above.

¹ <#489>
@tsibley tsibley force-pushed the trs/standalone/linux-aarch64 branch from 412548f to 3ef5c18 Compare November 7, 2025 06:59
GitHub released public runners.¹  This will ultimately let us use
standalone installation archives in our linux/arm64 Docker images.²

Changes to the standalone installer to follow separately³, as those need
to be held for merge until after the first release with these builds
available.

¹ <https://github.blog/changelog/2025-01-16-linux-arm64-hosted-runners-now-available-for-free-in-public-repositories-public-preview/>
² <nextstrain/docker-base#273>
³ <#490>
tsibley added a commit that referenced this pull request Nov 7, 2025
Conditions on the Nextstrain CLI version being requested, as aarch64
builds¹ will only be available going forward for new releases.  Assumes
the next release will be 10.4.2!

We must wait to merge this until after the first release (i.e. 10.4.2)
of the changes it depends on above.

¹ <#489>
@tsibley tsibley force-pushed the trs/standalone/linux-aarch64 branch from 3ef5c18 to f24763d Compare November 7, 2025 18:14
@tsibley
Copy link
Member Author

tsibley commented Nov 7, 2025

I believe CI should be passing now, but the test-standalone (os=ubuntu-22.04, target=x86_64-unknown-linux-gnu) job seems to be consistently hanging during an initial conda-incubator/setup-miniconda@v3. This feels like an issue with Conda or GitHub Actions or similar, but it's not immediately clear. I don't think this is related to the changes on this branch. (but it's possible!)

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.

2 participants