Skip to content

chore(deps): Revert "chore(deps): bump runs-on/action from 2.0.3 to 2.1.0 (#20980)"#21002

Merged
mbutrovich merged 1 commit intoapache:mainfrom
mbutrovich:revert-20980
Mar 17, 2026
Merged

chore(deps): Revert "chore(deps): bump runs-on/action from 2.0.3 to 2.1.0 (#20980)"#21002
mbutrovich merged 1 commit intoapache:mainfrom
mbutrovich:revert-20980

Conversation

@mbutrovich
Copy link
Copy Markdown
Contributor

@mbutrovich mbutrovich commented Mar 17, 2026

This reverts commit 11b9693.

Which issue does this PR close?

  • Closes #.

Rationale for this change

I noticed CI is not running on this PR opened today: #20998

See related Comet discussion at apache/datafusion-comet#3684 (comment)

image ASF blocks non-approved actions inside apache organization (by hash), so you either need to add it to https://github.com/apache/infrastructure-actions or rollback the update

We're now seeing it in DF as well:

Screenshot 2026-03-17 at 12 06 22 PM

What changes are included in this PR?

Are these changes tested?

Existing tests (make sure they actually run).

Are there any user-facing changes?

-No.

@mbutrovich mbutrovich added this pull request to the merge queue Mar 17, 2026
Merged via the queue into apache:main with commit 8142308 Mar 17, 2026
30 of 32 checks passed
@mbutrovich mbutrovich deleted the revert-20980 branch March 17, 2026 16:33
@alamb
Copy link
Copy Markdown
Contributor

alamb commented Mar 17, 2026

FYI @blaginin

@blaginin
Copy link
Copy Markdown
Member

thanks! need to merge apache/infrastructure-actions#537

de-bgunter pushed a commit to de-bgunter/datafusion that referenced this pull request Mar 24, 2026
….1.0 (apache#20980)" (apache#21002)

This reverts commit 11b9693.

## Which issue does this PR close?

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes apache#123` indicates that this PR will close issue apache#123.
-->

- Closes #.

## Rationale for this change

I noticed CI is not running on this PR opened today:
apache#20998

<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->

See related Comet discussion at
apache/datafusion-comet#3684 (comment)

> <img alt="image" width="1875" height="418"
src="https://private-user-images.githubusercontent.com/19199204/564414382-56caab4b-20d9-4d7b-b1ef-11de17ded2bc.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzM3NjM4MjUsIm5iZiI6MTc3Mzc2MzUyNSwicGF0aCI6Ii8xOTE5OTIwNC81NjQ0MTQzODItNTZjYWFiNGItMjBkOS00ZDdiLWIxZWYtMTFkZTE3ZGVkMmJjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjAzMTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwMzE3VDE2MDUyNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTVlOTAxYzhmNjFjMzEwZWMzY2E3M2JhMWVjYzUwZjBiY2IxN2NlNzdkYjNkN2MwMzFkZDllZjJiMzk1YTUzYWEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.IwLJ7-JDMYMr6qcO0WWHRsUgRhios73KuMl1a41nN2k">
> ASF blocks non-approved actions inside apache organization (by hash),
so you either need to add it to
https://github.com/apache/infrastructure-actions or rollback the update

We're now seeing it in DF as well:

<img width="865" height="335" alt="Screenshot 2026-03-17 at 12 06 22 PM"
src="https://github.com/user-attachments/assets/668a1dda-bf79-42f4-9472-acf8f7b3895e"
/>


## What changes are included in this PR?

<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->

- Revert apache#20980 

## Are these changes tested?

<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->

Existing tests (make sure they actually run).

## Are there any user-facing changes?

<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->

-No.

<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
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.

4 participants