Skip to content

No change for a PR to trigger release #6692

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

Merged
merged 1 commit into from
May 12, 2022

Conversation

yarikoptic
Copy link
Member

No description provided.

@yarikoptic yarikoptic added semver-internal Changes only affect the internal API release Create a release when this pr is merged labels May 11, 2022
@yarikoptic
Copy link
Member Author

will wait for CI just to make sure no surprises, will merge whennever all is ok

@yarikoptic
Copy link
Member Author

Actually -- I might replace it with another PR , please don't merge

@yarikoptic yarikoptic marked this pull request as draft May 11, 2022 19:48
@yarikoptic
Copy link
Member Author

well -- my idea was to just mark all those failing or erroring on windows with recent git-annex (attn @joeyh -- might be regressions) tests in #6617 as known. But those errors/fails seems grave enough to not just mark and forget (we have over 30 uses of @known.*windows), so although we might miss new extra fails, at least I will be constantly reminded (and will remind all of us) that we need to address those!!!

@yarikoptic yarikoptic marked this pull request as ready for review May 11, 2022 19:59
@yarikoptic
Copy link
Member Author

Anyways -- I think it is good, merging

@yarikoptic yarikoptic merged commit 4087a93 into datalad:maint May 12, 2022
@github-actions
Copy link

🚀 PR was released in 0.16.3 🚀

@yarikoptic yarikoptic deleted the enh-release branch July 11, 2022 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Create a release when this pr is merged released semver-internal Changes only affect the internal API
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant