Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency binaryage:devtools to v0.9.11 #15

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 25, 2019

Mend Renovate

This PR contains the following updates:

Package Type Update Change
binaryage:devtools dependencies patch 0.9.4 -> 0.9.11

Release Notes

binaryage/cljs-devtools

v0.9.11: 0.9.11

Compare Source

Minor improvements

The main reason for this release is a fix to properly handle ##NaN and ##Inf (#​54).

Also I decided to archive cljs-devtools-sample repo and merge its history under examples/lein in this repo and continue from there.

Notable commits:

c588d67 fix misspelled header-post-handler in defaults (close #​48)
5b935af readme: point to new examples subdirectory
02bb9ad async: work around warning about "setImmediate_ is not public"
49dfc24 properly handle ##NaN and ##Inf (close #​54)
f394d71 add tests for issue #​44, not reproducible

All new work: binaryage/cljs-devtools@v0.9.10...v0.9.11

v0.9.10: 0.9.10

Compare Source

Recognise MapEntry

Notable commits:

ca7e096 require devtools.toolbox macros into cljs namespace
adcddd1 Add cljs.core/MapEntry as a well known type (#​41)

All new work: binaryage/cljs-devtools@v0.9.9...v0.9.10

v0.9.9: 0.9.9

Compare Source

The :async feature is no longer needed

Chrome devs finally implemented support for long async stacktraces for goog.async.nextTick (https://github.com/binaryage/cljs-devtools/issues/20).

https://bugs.chromium.org/p/chromium/issues/detail?id=661705

Notable commits:

6dc3c10 print an info message that the :async feature is no longer needed

All new work: binaryage/cljs-devtools@v0.9.8...v0.9.9

v0.9.8

Compare Source

Checked Array Access

The library now plays well when you enable :checked-arrays in your project. Checked Array Access is a new feature of recent ClojureScript compiler.

Notable commits:

ab0b3c1 switch to unchecked-aget/aset to prevent :checked-arrays warnings

All new work: binaryage/cljs-devtools@v0.9.7...v0.9.8

v0.9.7: 0.9.7

Compare Source

A hot-fix release

Forgot to bump env-config because lein-ancient was broken for this project.clj on my machine for some unknown reason.

Notable commits:

11d86fe project: bump env-config to "0.2.2"

All new work: binaryage/cljs-devtools@v0.9.6...v0.9.7

v0.9.6: 0.9.6

Compare Source

A hot-fix release

I had a bug in packaging code. Releases v0.9.5 had missing downstream dependencies.

Notable commits:

b18b638 project: remove broken dependencies setup in :lib profile

All new work: binaryage/cljs-devtools@v0.9.5...v0.9.6

v0.9.5: 0.9.5

Compare Source

A maintenance release

Notable commits:

585c2c6 variadic methods in protocols have never been supported
046ea60 centralize console selection via context

All new work: binaryage/cljs-devtools@v0.9.4...v0.9.5


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/binaryage-devtools-0.x branch from 383defb to afcd5fb Compare November 21, 2019 14:15
@renovate renovate bot changed the title Update dependency binaryage:devtools to v0.9.10 Update dependency binaryage:devtools to v0.9.11 Nov 21, 2019
@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

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.

1 participant