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

[ADAP-1071] [Bug] latest and 1.x.latest tags for ghcr Docker releases are stale #957

Closed
2 tasks done
Tracked by #7571
dbeatty10 opened this issue Dec 11, 2023 · 1 comment · Fixed by #1004
Closed
2 tasks done
Tracked by #7571
Labels
bug Something isn't working support

Comments

@dbeatty10
Copy link
Contributor

Is this a new bug in dbt-spark?

  • I believe this is a new bug in dbt-spark
  • I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

Look at https://github.com/dbt-labs/dbt-spark/pkgs/container/dbt-spark/versions?filters%5Bversion_type%5D=tagged

1.3.0 is tagged as latest:

image

Expected Behavior

1.6.1 is tagged as latest and 1.6.latest:

image

And the rest of the 1.x minor versions have 1.x.latest tags as well.

Steps To Reproduce

See current behavior above.

Relevant log output

No response

Environment

- OS:
- Python:
- dbt-core:
- dbt-spark:

Additional Context

No response

@dbeatty10 dbeatty10 added bug Something isn't working triage labels Dec 11, 2023
@github-actions github-actions bot changed the title [Bug] latest and 1.x.latest tags for ghcr Docker releases are stale [ADAP-1071] [Bug] latest and 1.x.latest tags for ghcr Docker releases are stale Dec 11, 2023
@dbeatty10
Copy link
Contributor Author

dbt-labs/dbt-core#9495 fixes the underlying issue (thank you @mikealfare !), and this particular issue will be resolved for each 1.x version of this adapter upon its next patch release.

We are choosing not to address any un-supported versions at this time, so <=1.4.x will not be updated.

Here are the most recent ones for the supported versions of dbt-spark in PyPI:

  • 1.7.1
  • 1.6.2
  • 1.5.3

So this will be completely resolved for >=1.5.x when each of the following are released (but only if each is released prior to falling out of support):

  • 1.7.2
  • 1.6.3
  • 1.5.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working support
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants