Ben Henning b5f2d576fa fix: Make the 'welcome new contributors' workflow run again (#9448) ...

## The basics

- [x] I [validated my changes](https://developers.google.com/blockly/guides/contribute/core#making_and_verifying_a_change)

## The details
### Resolves

Fixes #9447

### Proposed Changes

Pin the `actions/first-interactions` action to v1.3.0 and update the input parameters. Configure Dependabot to no longer try to upgrade this version.

### Reason for Changes

There are three sets of failures being addressed here:
1. `v3.0.0` introduces a breaking changes by renaming the input names.
2. `v3.1.0` introduces a breaking change that somehow enforces `issue_message` being required which isn't being defined for Blockly (we only welcome on PRs). This hasn't been addressed by the action author so this PR pins to v3.0.0 to go back to a working version.\*
3. `v2` introduced a breaking behavioral change that caused all runs of the workflow to outright fail by not being compatible with `pull_request_target`.

\* Technically it was broken when upgraded in #9323 due to a warning (rather than error) enforcing the now-required parameters. That was hiding a failure introduced when upgraded in #9274 that outright broke the workflow due to it running with `pull_request_target`.

### Test Coverage

The team doesn't utilize automated tests for the workflow configurations themselves thus verifying them through running CI is sufficient.

https://github.com/BenHenning/blockly/pull/16#pullrequestreview-3400731300 demonstrates this passing and working correctly with a merged in version of this branch (since the workflow uses `pull_request_target` it cannot be verified in this PR's CI workflow) for a 'new' contributor (thanks for the help @rpbourret and @maribethb).

### Documentation

No documentation changes are needed for this workflow configuration change.

### Additional Information

Nothing to add that's not above or in the filed bug.

2025-10-30 10:53:35 -07:00

1.0 KiB

Raw Blame History

View Raw