| Age | Commit message (Collapse) | Author |
|---|
|
|
|
* [Win32] set flag to allow unprivileged users to create symlinks
Notes:
Merged-By: nobu <nobu@ruby-lang.org>
|
|
|
|
It was using the same one as original AppVeyor's notification, but it's
just inconsistent with others like Travis and GitHub Actions.
|
|
by marking continue-on-error.
I dropped it to test Slack notification, and I finished to test it.
|
|
by using toJson with fields.
|
|
for macOS / Windows as well.
Docker-based GitHub Action does not work on these OSes.
|
|
|
|
|
|
This reverts commit d8807e8b1a9d09ee1543e18618b4ef7e8203c616.
We'd need more features. Reverting to customize this later.
|
|
https://github.com/8398a7/action-slack
https://github.com/marketplace/actions/action-slack
|
|
to clarify what's running for every commit.
|
|
|
|
|
|
for consistency. In the pull request, `before_test` was dropped only for
msys2 to fix msys2-only failure. But there's no need to keep it
inconsistent now.
|
|
* appveyor.yml - OpenSSL vc120 -> 1.0.2, vc140 -> 1.1.1
* Try just using build_script
|
|
|
|
|
|
https://github.com/bundler/bundler/commit/8ef571ed4e
|
|
The version we're vendoring actually relaxed this restriction back to
2.3.0+, so we can always use the vendored version.
https://github.com/bundler/bundler/commit/d366cbfe5d
|
|
Instead, make sure we always load the local copy of bundler during
specs, and never end up using the default copy.
https://github.com/bundler/bundler/commit/ac655ffeda
|
|
If we use system bundler, when booting the "outermost" bundler process,
bundler will save the path to the system bundler in BUNDLE_BIN_PATH, and
use it again when booting the "innermost" bundler process (`bundle exec
echo foo`).
That means that second process will use the system bundler path again.
However, we have `-rsupport/hax` in RUBYOPT, so that file will load from
the local copy of bundler, and that file will load `bundler/version`
from the project (not from system), because -Ilib is in the LOAD_PATH.
That will end up causing redefinition errors because the same constant
will be loaded from two different locations.
In general, this is expected behavior, normally you will wrap the
process with `Bundler.with_original_env` to reset the environment.
However, the easiest fix here is to not use system bundler, because it's
not really necessary and thus doesn't help the readability of the spec.
https://github.com/bundler/bundler/commit/a3d72a34ab
|
|
https://github.com/bundler/bundler/commit/789dd1864f
|
|
https://github.com/bundler/bundler/commit/e4cbb91b7d
|
|
https://github.com/bundler/bundler/commit/fb587b9ebb
|
|
https://github.com/bundler/bundler/commit/f9cb39e614
|
|
https://github.com/bundler/bundler/commit/3995b3345d
|
|
https://github.com/bundler/bundler/commit/792d724752
|
|
So I can add another context that doesn't run the `before` block.
https://github.com/bundler/bundler/commit/06d0acc45a
|
|
https://github.com/bundler/bundler/commit/6678747fae
|
|
Previously `bundle doctor` would fail on any bundle that does not
include git gems or plugins. This is because the previously used
`Bundler.home` does not exist unless the bundle includes git gems or
plugins. For example, with `bundle config set path .bundle`, it points
to which does not exist unless this kind of gems exist in the Gemfile.
The name `Bundler.home` is really unfortunate, it should probably be
have more descriptive name, and be private. But for now I just want to
make `bundle doctor` usable.
https://github.com/bundler/bundler/commit/5531a18c1e
|
|
gems only appear once per group
https://github.com/bundler/bundler/commit/d18a83109e
|
|
|
|
Like macos.yml, we don't need to ignore `make check` failure.
|
|
|
|
|
|
|
|
To reproduce this bug, type one character into irb, then press the
delete key on your keyboard.
|
|
|
|
|
|
|
|
|
|
|
|
Installed path may contain symbolic links.
|
|
VM_DEBUG_MODE has been used only here.
|
|
|
|
|
|
Gem::Specification#files.
|
|
|
|
|
