Skip to content
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.

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

chore: Pin asdf to 0.15.0 to avoid notice about 0.16 Go rewrite #1195

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jzimbel-mbta
Copy link
Member

Summary of changes

Asana Ticket: ad hoc
(analogue to this ticket for gtfs_creator)

This prevents asdf from printing notices about the v0.16 Go rewrite every time it runs (i.e., between every single shell command issued during CI)

Reviewer Checklist

  • Meets ticket's acceptance criteria
  • Any new or changed functions have typespecs
  • Tests were added for any new functionality (don't just rely on Codecov)
  • This branch was deployed to the staging environment and is currently running with no unexpected increase in warnings, and no errors or crashes.

@jzimbel-mbta jzimbel-mbta requested a review from a team as a code owner April 2, 2025 14:55
@jzimbel-mbta jzimbel-mbta requested review from rudiejd and removed request for a team April 2, 2025 14:55
@@ -23,6 +23,8 @@ jobs:
# only run `asdf install` if we didn't hit the cache
- uses: asdf-vm/actions/install@v1
if: steps.asdf-cache.outputs.cache-hit != 'true'
with:
asdf_branch: v0.15.0

build:
name: Build Elixir
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you would also have to pin asdf for this job

@rudiejd
Copy link
Contributor

rudiejd commented Apr 2, 2025

is it worth just following the migration guide here so we can run the latest and greatest asdf? what is blocking us from migrating to 0.16?

@cmaddox5
Copy link
Contributor

cmaddox5 commented Apr 4, 2025

is it worth just following the migration guide here so we can run the latest and greatest asdf? what is blocking us from migrating to 0.16?

Because this is a 3rd party action, we don't have control of the default version used. There is apparently a recent fix that has been merged, but there doesn't seem to be a release that contains the change. We could use the commit hash instead of the major version (we're a couple behind anyway). Then we wouldn't need to pin.

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