| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
So it's shorter on CI and the hint about how the fix the failure shows
up. It's going to print a diff locally too, but that should be fine.
|
|
|
|
|
|
| |
This makes it clear what to do when the CI check
fails and should remove a few minutes of confusion
for people seeing this for the first time.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [octokit/request-action](https://github.com/octokit/request-action) from 4579f9e1e690974421f9f6928a30fb448e967c60 to 52ce92ce3185e00e2425f043c3e9509121929aea.
- [Release notes](https://github.com/octokit/request-action/releases)
- [Commits](https://github.com/octokit/request-action/compare/4579f9e1e690974421f9f6928a30fb448e967c60...52ce92ce3185e00e2425f043c3e9509121929aea)
---
updated-dependencies:
- dependency-name: octokit/request-action
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
|
|
|
| |
It's not that important for ruby/ruby to keep them up to date.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [ruby/setup-ruby](https://github.com/ruby/setup-ruby) from 1.125.0 to 1.126.0.
- [Release notes](https://github.com/ruby/setup-ruby/releases)
- [Commits](https://github.com/ruby/setup-ruby/compare/de6f5b9c340068d049670c6b6ae8dc94cff4667a...c7079efafd956afb5d823e8999c2506e1053aefa)
---
updated-dependencies:
- dependency-name: ruby/setup-ruby
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 2.1.33 to 2.1.35.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/github/codeql-action/compare/v2.1.33...b2a92eb56d8cb930006a1c6ed86b0782dd8a4297)
---
updated-dependencies:
- dependency-name: github/codeql-action
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
|
|
| |
* YJIT: check that we correctly auto-enable YJIT on Linux
YJIT should be automatically built on Linux x86-64 when
rustc is present, and we should see +YJIT in the version string.
* Use miniruby rather than system ruby
|
|
|
|
|
| |
It may cause parse errors in some other sh even in never executed
parts.
|
| |
|
| |
|
|
|
| |
Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
|
|
|
|
| |
https://github.com/ruby/ruby/actions/runs/3560006749/jobs/5979749144
|
|
|
|
|
|
|
|
|
| |
We've disabled MJIT CI on GitHub Actions for a while. It's convenient
that fork repositories need to see failures or disable it.
We should remove unused CI by default instead of silently disabling it.
Since I saw --mjit-wait passed on my fork, I'd like to try running
--mjit-wait one.
|
| |
|
| |
|
|
|
| |
Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
|
| |
|
| |
|
|
|
|
|
|
|
| |
It seems like dependabot supports updating the `# vX.Y.Z` comment.
The reason why I disabled this was that it failed to update this, but
maybe it was because it had `, checking sha`. Let me try it again with
that removed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 3.1.0 to 3.1.1.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](https://github.com/actions/upload-artifact/compare/3cea5372237819ed00197afe530f5a7ea3e805c8...83fd05a356d7e2593de66fc9913b3002723633cb)
---
updated-dependencies:
- dependency-name: actions/upload-artifact
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before:
```
Reducing stack by rule 639 (line 5062):
$1 = token "integer literal" (1.0-1.1: 1)
-> $$ = nterm simple_numeric (1.0-1.1: )
```
After:
```
Reducing stack by rule 641 (line 5078):
$1 = token "integer literal" (1.0-1.1: 1)
-> $$ = nterm simple_numeric (1.0-1.1: NODE_LIT)
```
`"<*>"` is supported by Bison 2.3b (2008-05-27) or later.
https://git.savannah.gnu.org/cgit/bison.git/commit/?id=12e3584054c16ab255672c07af0ffc7bb220e8bc
Therefore developers need to install Bison 2.3b+ to build ruby from
source codes if their Bison is older.
Minimum version requirement for Bison is changed to 3.0.
See: https://bugs.ruby-lang.org/issues/19068 [Feature #19068]
|
|
|
|
| |
results for Ruby code
|
|
|
|
| |
The CI for MinGW has used it.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The previous one was the url of this notification action, but we want to
see a link to Cirrus CI.
This code follows https://cirrus-ci.org/guide/notifications/.
Also, head_branch was null only for pull requests from a fork, so we can
use it for branch-based filtering, which is good.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
It looks like Cirrus doesn't natively support notifications and they
recomment to use GitHub Actions for it.
https://cirrus-ci.org/guide/notifications/
Because I don't know what the payload looks like, I just added a basic
payload and dumped GitHub context so that we could improve it later.
|
|
|
|
|
|
|
|
|
|
| |
It's moved from k0kubun to ruby org.
Also, we don't need JavaScript eval to generate branch if we use
github.ref_name, so v3.0.0 is a version that doesn't use eval.
Co-Authored-By: Nobuyoshi Nakada <nobu@ruby-lang.org>
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
| |
|
|
|
|
|
|
|
|
| |
because you have to manually update the version tag comment.
It feels unsafe to trust third party git tags when you need to pass
MATZBOT_GITHUB_TOKEN to it. Git commit sha alone isn't human-readable
and I'm reluctant to remove the comment either. It doesn't seem worth
the effort to review changes for every release of this action.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [necojackarc/auto-request-review](https://github.com/necojackarc/auto-request-review) from 0.7.0 to 0.8.0.
- [Release notes](https://github.com/necojackarc/auto-request-review/releases)
- [Commits](https://github.com/necojackarc/auto-request-review/compare/e08cdffa277d50854744de3f76230260e61c67f4...b5e81876454003a4ccb9b89cb205c67d77d7035b)
---
updated-dependencies:
- dependency-name: necojackarc/auto-request-review
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit d152ac677cffdbc136530dd56a56c42518d29ea4, "Make
CodeQL ignore syntax_suggest because of the performance problem".
Probably all instances seem to already have updated to 2.10.5 now.
|
| |
|
| |
|
|
|
|
| |
Make the job names more understandable and avoid testing too many
duplicated things.
|
|
|
|
|
|
|
|
| |
Visual Studio 2019 GitHub Actions has been super unstable. Somehow nmake
test-spec triggers rebuilding the interpreter and fails.
usa suggested a possibility of test-all leaving something impacting
test-spec. I'd like to try this patch and see what happens.
|
|
|
|
| |
The matrix doesn't have `os`.
|
|
|
|
| |
See https://discourse.llvm.org/t/llvm-15-0-0-release/65099
|