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 v1 #31

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 8, 2020

Mend Renovate

This PR contains the following updates:

Package Type Update Change
binaryage:devtools dependencies major 0.9.10 -> 1.0.6

Release Notes

binaryage/cljs-devtools

v1.0.6: 1.0.6

Compare Source

A maintenance release

Notable commits:

8072ad9 Fix path indexes after max-number-body-items

All new work: binaryage/cljs-devtools@v1.0.5...v1.0.6

v1.0.5: 1.0.5

Compare Source

A maintenance release

Notable commits:

c10a069 fix #​63: compiler warning
5b798a3 Path generation performance improvements

All new work: binaryage/cljs-devtools@v1.0.4...v1.0.5

v1.0.4: 1.0.4

Compare Source

Add support for path annotations

This is just a maintenance release with added special feature for re-frame-10x as described in the issue #​56.

Notable commits:

638e029 a proof of concept for issue #​56
b87b922 Improve path generation

All new work: binaryage/cljs-devtools@v1.0.3...v1.0.4

v1.0.3: 1.0.3

Compare Source

A maintenance release

Notable commits:

7483b32 follow CLJS-3271

All new work: binaryage/cljs-devtools@v1.0.2...v1.0.3

v1.0.2: 1.0.2

Compare Source

Good news :-)

Chrome developers reconsidered removing the custom formatters feature. You can follow further discussion in issue #​55.

I'd like to thank Chrome dev team for being responsive and open for discussion.
And I also thank all users who expressed that the feature is important and should be preserved is some form.

Notable commits:

52e4efe Revert "formatters: when installing, display a warning related to issue 55"

All new work: binaryage/cljs-devtools@v1.0.1...v1.0.2

v1.0.1: 1.0.1

Compare Source

Sad news :-(

Chrome devs decided to phase out support for custom formatters. This will likely happen in the near future.

The point of this release is to add a warning so people are aware of this comming change. We track this in issue #​55.

Notable commits:

76a76f8 display a warning related to issue #​55
8dd8b9c munging: do not rely on goog.dependencies_.nameToPath

All new work: binaryage/cljs-devtools@v1.0.0...v1.0.1

v1.0.0: 1.0.0

Compare Source

  • added deps.edn for people who want to consume this library via deps git location
  • created new minimal example projects shadow and deps
  • removed configurability via env variables (cljs-devtools has zero dependencies now)
Notable commits:

d0b64d7 remove configurability via env variables
c7c6f24 introduce minimal deps-based project example
700d9e5 add minimal shadow-cljs example
3f93837 add deps.edn for people who want to consume this via deps
8c30872 improve get-node-info to not trigger "pause on caught exceptions"
be786b9 drop deprecated API
a56f54c tests: switch from phantom to puppeteer

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

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


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-1.x branch from 1021c3a to bccb63c Compare July 1, 2020 13:48
@renovate renovate bot force-pushed the renovate/binaryage-devtools-1.x branch from bccb63c to edf3478 Compare April 26, 2021 15:57
@renovate renovate bot force-pushed the renovate/binaryage-devtools-1.x branch from edf3478 to c35e8c9 Compare October 18, 2021 20:18
@renovate renovate bot force-pushed the renovate/binaryage-devtools-1.x branch from c35e8c9 to 0d35b1f Compare March 7, 2022 17:38
@renovate renovate bot force-pushed the renovate/binaryage-devtools-1.x branch from 0d35b1f to d1cb0af Compare April 24, 2022 23:13
@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.

None yet

1 participant