This repository has been archived by the owner on Apr 17, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.2.5
->4.3.4
7.1.2
->7.1.5
4.1.5
->4.1.7
7.3.2
->7.3.5
4.6.6
->4.6.7
7.5.1
->7.5.2
3.4.6
->3.4.10
6.0.3
->6.0.4
2.7.0
->2.11.0
16.5.0
->16.5.2
4.2.0
->4.3.7
3.0.8
->3.1.1
4.1.1
->4.3.4
3.0.0
->3.0.1
14.5.8
->14.7.0
1.6.6
->1.8.1
6.2.2
->6.2.3
0.19.1
->0.21.2
0.9.0
->0.15.5
1.1.1
->1.2.2
0.5.16
->0.5.21
0.9.16
->0.11.0
8.5.2
->8.10.2
0.15.3
->0.23.28
3.7.2
->3.9.10
3.3.3
->3.4.0
Release Notes
lancedikson/bowser
v2.11.0
Compare Source
Parser#is
method (#437)v2.10.0
Compare Source
v2.9.0
Compare Source
v2.8.1
Compare Source
v2.8.0
Compare Source
browserify/browserify
v16.5.2
Compare Source
Upgrade browser-resolve to v2.
https://github.com/browserify/browserify/pull/1973
v16.5.1
Compare Source
Remove deprecated
mkdirp
version in favour ofmkdirp-classic
.browserify/browserify@00c913f
Pin dependencies for Node.js 0.8 support.
https://github.com/browserify/browserify/pull/1939
chaijs/chai
v4.3.7
Compare Source
What's Changed
Full Changelog: chaijs/chai@v4.3.6...v4.3.7
v4.3.6
Compare Source
Update loupe to 2.3.1
v4.3.5
Compare Source
fca5bb1
747eb4e
022c2fa
5276af6
c8a4e00
v4.3.4
Compare Source
This fixes broken inspect behavior with bigints (#1321) (#1383) thanks @vapier
v4.3.3
: / 2021-03-03Compare Source
This reintroduces
Assertion
as an export in the mjs file. See https://github.com/chaijs/chai/pull/1378 & https://github.com/chaijs/chai/issues/1375v4.3.2
: / 2021-03-03Compare Source
This fixes a regression in IE11. See https://github.com/chaijs/chai/pull/1380 & https://github.com/chaijs/chai/issues/1379
v4.3.1
: / 2021-03-02Compare Source
This releases fixed an engine incompatibility with 4.3.0
The 4.x.x series of releases will be compatible with Node 4.0. Please report any errors found in Node 4 as bugs, and they will be fixed.
The 5.x.x series, when released, will drop support for Node 4.0
This fix also ensures
pathval
is updated to1.1.1
to fix CVE-2020-7751v4.3.0
: / 2021-02-04Compare Source
This is a minor release.
Not many changes have got in since the last release but this one contains a very important change (#1257) which will allow
jest
users to get better diffs. From this release onwards,jest
users will be able to see which operator was used in their diffs. Theoperator
is a property of theAssertionError
thrown when assertions fail. This flag indicates what kind of comparison was made.This is also an important change for plugin maintainers. Plugin maintainers will now have access to the
operator
flag, which they can have access to through an
utilmethod called
getOperator`.Thanks to all the amazing people that contributed to this release.
New Features
contain.oneOf
to take an array of possible values (@voliva)closeTo
error message will now inform the user when adelta
is required (@eouw0o83hf)Docs
Tests
useProxy
config is checked inoverwriteProperty
(@vieiralucas)contain.oneOf
(@voliva )Chores
nickmerwin/node-coveralls
v3.1.1
: Maintenance / Security updatesCompare Source
exec
forexecFile
. Credit: Adar Zandberg from the CxSCA AppSec team at Checkmarx.devDependencies
v3.1.0
: Improved CircleCI / Travis parallelism supportCompare Source
service_job_number
for parallelism in Travis and CircleCI (#290)705c3b5
eb6dc35
This is a
minor
release due to the change in behavior for CircleCI, which now uses the Workflow ID to merge parallel coverage jobs:v3.0.14
: MaintenanceCompare Source
59a57e2
a0c6941
@XhmikosR1615297
3647673
@XhmikosRff21930
@lpincav3.0.13
: Maintenance releaseCompare Source
v3.0.12
Compare Source
v3.0.11
: COVERALLS_SERVICE_NUMBER environment variable supportCompare Source
Improved:
v3.0.10
: CodeFresh support, MaintenanceCompare Source
Added:
Improved:
Updated:
v3.0.9
: Maintenance, dependency refinementCompare Source
debug-js/debug
v4.3.4
Compare Source
What's Changed
New Contributors
Full Changelog: debug-js/debug@4.3.3...4.3.4
v4.3.3
Compare Source
Patch Release 4.3.3
This is a documentation-only release. Further, the repository was transferred. Please see notes below.
Thank you to @taylor1791 and @kristofkalocsai for their contributions.
Repository Migration Information
I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.
Q: What impact will this have on me?
In most cases, you shouldn't notice any change.
The only exception I can think of is if you pull code directly from https://github.com/visionmedia/debug, e.g. via a
"debug": "visionmedia/debug"
-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.Q: What are the security implications of this change?
If you pull code directly from the old URL, you should update the URL to https://github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.
Even in such a case, however, the officially released package on npm (
debug
) would not be affected. That package is still very much under control (even more than it used to be).Q: What should I do if I encounter an issue related to the migration?
Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.
Q: Why was this done as a 'patch' release? Isn't this breaking?
No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.
Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.
I understand there are a lot of edge cases so please open issues as needed so I can assist in any way necessary.
Q: Why was the repository transferred?
I'll just list them off in no particular order.
debug
ecosystem intends to grow beyond a single package, and since new packages could not be created in the old org (nor did it make sense for them to live there), a new org made the most sense - especially from a security point of view.Q: Was this approved?
Yes.[archive]
Q: Do I need to worry about another migration sometime in the future?
No.
v4.3.2
Compare Source
Patch release 4.3.2
.enabled
checks (#799)Thank you @omg!
v4.3.1
Compare Source
Patch release 4.3.1
v4.3.0
Compare Source
Minor release
debugInstance.destroy()
. Future major versions will not have this method; please remove it from your codebases as it currently does nothing.v4.2.0
Compare Source
Minor Release
console.debug
in the browser only when it is available (#600)"engines"
key to package.jsonselectColor
(#747)supports-color
as an optional peer dependencysindresorhus/del-cli
v3.0.1
Compare Source
922e9fe
graphql/graphql-js
v14.7.0
Compare Source
v14.7.0 (2020-07-06)
New Feature 🚀
Committers: 1
v14.6.0
Compare Source
v14.6.0 (2020-01-27)
New Feature 🚀
Committers: 1
pimterry/loglevel
v1.8.1
Compare Source
v1.8.0
Compare Source
v1.7.1
Compare Source
v1.7.0
Compare Source
v1.6.8
Compare Source
v1.6.7
Compare Source
mochajs/mocha
v6.2.3
Compare Source
🔒 Security Fixes
httptoolkit/mockttp
v0.21.2
Compare Source
v0.21.1
Compare Source
v0.21.0
Compare Source
v0.20.4
Compare Source
v0.20.3
Compare Source
v0.20.2
Compare Source
v0.20.1
Compare Source
v0.20.0
Compare Source
v0.19.3
Compare Source
v0.19.2
Compare Source
aerogear/offix
v0.15.5
Compare Source
Fixing minor releng issues. No actual functional changes
v0.15.4
Compare Source
Updated internal packages and bug fixes
v0.15.3
Compare Source
Updated internal packages and bug fixes
v0.15.2
Compare Source
Patch release that updates dependencies and some minor docs fixes.
Bug fixes
52b912e
: fix: bump react version to meet react-offix-hooks peer depDocs changes
54ce1f2
: fix: Remove unmaintained offix android916b49a
: docs: fixing typos0e20ad0
: Update ref-conflict-client.mdv0.15.1
Compare Source
Patch release that fixes a couple of bugs, updates dependencies, adds a new example app, and some minor docs fixes.
Bug Fixes
55b3545
fix: id overwrite issue in optimistic responses52dd303
Runtime config validation Closes #283 (#402)New Example App
113f4e8
feat: add unstyled react native example appDocs changes
64ab7e3
chore: add link to example app for Reactd76725b
fix: link error with React Native doc.c604961
chore: add link to example app in docsa83f5b8
fix: remove unnecessary step in react example readmev0.15.0
Compare Source
feat: allow for adding conflict listeners after client creation (#393)
Adds
addConflictListener
andremoveConflictListener
methods toApolloOfflineClient
.v0.14.0
Compare Source
Notable Commits
a9ee41d
fix: persist queue entries after updating optimistic ids (#389)7ffae63
fix: improve queue handling of optimistic ids + InputMapper (#381)6d736d8
fix: react example app build issue (#387)7d8ea82
breaking: refactor offline mutate (#378)05625f2
breaking: refactor network status interface (#368)60c745c
chore: Stop generating source maps (#375)v0.13.2
Compare Source
Add
useNetworkStatus
React hook which can be used to build components that render differently depending on the network state.v0.13.1
Compare Source
0.13.1 fixes package install issues that were introduced in 0.13.0. It also introduces some minor dependency updates.
v0.13.0
Compare Source
0.13.0
The 0.13.0 release is a release contains a couple of bug fixes, dependency updates and the new ability to configure your own
CachePersistor
object as requested in #273 and #281.The CachePersistor is used by the client to persist the Apollo Cache across application restarts. Pass your own instance to override the one that is created by default.
Example:
Note: if using TypeScript, you may need to declare the cachePersistor as follows
const cachePersistor = new CachePersistor<object>(...options)
or you may experience compiler errors.This example uses
createDefaultCacheStorage
to create the default IndexedDB based storage driver.The storage can be swapped depending on the platform. For example
window.localstorage
in older browsers orAsyncStorage
in React Native.v0.12.0
Compare Source
0.12.0
The 0.12.0 release brings a new
offix-client-boost
package. This package is a batteries-included wrapper around theoffix-client
that bringseverything needed to get started with GraphQL quickly. This includes a cache and support for subscriptions and file uploads.
This release also provides new documentation for React Native, Angular and Ionic/Cordova.
Check out the new documentation at offix.dev.
v0.11.0
Compare Source
0.11.0
The 0.11.0 release simplifies the creation of offline clients.
Breaking Changes
OfflineClient replaced with ApolloOfflineClient
The
OfflineClient
class has been replaced withApolloOfflineClient
.OfflineClient
was a wrapper that would internally create anApolloClient
which could be accessed after initialization. The flow looked something like this.The new
ApolloOfflineClient
directlyextends
ApolloClient
which makes initialization simpler and more flexible as all of the standard Apollo Client options are supported.Initialization is slightly different, mainly, and
ApolloLink
must be passed that can connect with the GraphQL server. See the example code below.v0.10.0
Compare Source
0.10.0
The
0.10.0
release builds upon the0.9.0
release and adds two new packages.offix-scheduler
andoffix-conflicts-client
offix-scheduler
offix-scheduler
now holds the core functionalities of the Offix project. That includes queueing, scheduling, persistence and fulfilment of offline operations.offix-scheduler
can and will be used to create new clients in the future that are not based on Apollo Client. Clients we are investigating are URQL (see https://github.com/aerogear/offix/issues/235), Relay (see https://github.com/aerogear/offix/issues/236) and plain HTTP/REST.offix-client
now usesoffix-scheduler
under the hood.There have been no functional changes to
offix-client
and everything should remain the same.ALMaclaine/replace
v1.2.2
Compare Source
v1.2.1
Compare Source
v1.2.0
Compare Source
v1.1.5
Compare Source
v1.1.4
Compare Source
v1.1.3
Compare Source
v1.1.2
Compare Source
evanw/node-source-map-support
v0.5.21
Compare Source
v0.5.20
Compare Source
v0.5.19
Compare Source
v0.5.18
Compare Source
v0.5.17
Compare Source
apollostack/subscriptions-transport-ws
v0.11.0
Compare Source
graphql@16
and bump minimal supported version to be[email protected]
. As part of this change signatures forExecuteFunction
andSubscribeFunction
were changed.@IvanGoncharov in #902
v0.10.0
Compare Source
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.