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

update xattr to 1.1.3 #348

Merged
merged 1 commit into from
Jun 4, 2024
Merged

Conversation

sunshowers
Copy link
Contributor

xattr 1.0.0 through 1.1.2 have a bug
(Stebalien/xattr#48). Bump the requirement so that downstream dependents get the latest version.

xattr 1.0.0 through 1.1.2 have a bug
(Stebalien/xattr#48). Bump the requirement so that
downstream dependents get the latest version.
@adamqqqplay
Copy link
Contributor

@sunshowers Thanks! Currently xattr has released v1.3.1, can we bump to this version?

@sunshowers
Copy link
Contributor Author

Sure, note that I'm not a maintainer so you may wish to write your own PR.

@cgwalters cgwalters mentioned this pull request Jun 4, 2024
@alexcrichton
Copy link
Owner

Thanks!

I'll also note that technically this isn't necessary since these versions are all "1.x.x" compatible meaning that downstream consumers can always update. This change works by preventing tar from being used with previous versions (with the next release of tar)

@alexcrichton
Copy link
Owner

Also sorry for the delay on merging :(

@alexcrichton alexcrichton merged commit c74d62a into alexcrichton:main Jun 4, 2024
7 checks passed
@sunshowers
Copy link
Contributor Author

Thanks! The problem is not that downstream dependents can't update, it's that they won't update transitive deps unless prodded.

@sunshowers sunshowers deleted the update-xattr branch June 4, 2024 17:02
ararslan pushed a commit to ararslan/binstall-tar that referenced this pull request Jun 6, 2024
xattr 1.0.0 through 1.1.2 have a bug
(Stebalien/xattr#48). Bump the requirement so that
downstream dependents get the latest version.

(cherry picked from commit c74d62a)
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.

None yet

3 participants