Skip to content

Conversation

@dependabot-preview
Copy link
Contributor

Bumps mini_racer from 0.2.1 to 0.2.2.

Changelog

Sourced from mini_racer's changelog.

  • 26-09-2018

  • 0.2.2

    • WORKAROUND: RUBY_PLATFORM is hardcoded on Ruby compile and can not be
      trusted for feature detection, use a different technique when checking for
      macOS Mojave
  • 25-09-2018

  • 0.2.1

    • FEATURE: Mojave macOS support
  • 06-07-2018

  • 0.2.0

    • FEATURE: context#call to allow for cheaper invocation of functions
    • FIX: rare memory leak when terminating a long running attached function
    • FIX: rare segfault when terminating a long running attached function
    • FIX: Reimplement Isolate#idle_notification using idle_notification_deadline, API remains the same ignisf
    • Account for changes in the upstream V8 API ignisf
    • Support for libv8 6.7

23-08-2017

  • 0.1.15

    • bump dependency of libv8 to 6.3

23-08-2017

  • 0.1.14

    • libv8 erronuously bumped to beta, reverted change

23-08-2017

  • 0.1.13

    • Fix: amend array buffer allocator to use v8 6.0 compatible allocator ignisf

18-07-2017

  • 0.1.12

    • Feature: upgrade libv8 to 5.9
    • Fix: warning when runnin with ruby warnings enabled (missed disposed initialize)

18-07-2017

... (truncated)
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

Bumps [mini_racer](https://github.com/discourse/mini_racer) from 0.2.1 to 0.2.2.
- [Release notes](https://github.com/discourse/mini_racer/releases)
- [Changelog](https://github.com/discourse/mini_racer/blob/master/CHANGELOG)
- [Commits](rubyjs/mini_racer@v0.2.1...v0.2.2)

Signed-off-by: dependabot[bot] <support@dependabot.com>
@coveralls
Copy link

Coverage Status

Coverage remained the same at 78.782% when pulling 5afa053 on dependabot/bundler/mini_racer-0.2.2 into 7020c0b on master.

@indocomsoft indocomsoft merged commit 3588bae into master Sep 26, 2018
@dependabot-preview dependabot-preview bot deleted the dependabot/bundler/mini_racer-0.2.2 branch September 26, 2018 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants