Skip to content

0.12.0 appears to have been published to npm as 0.13.0 #35

Description

@mmalecki
  1. What version of the module is the issue happening on? Does the issue happen on latest version?
    0.12.0 / 0.13.0 ;)
  2. What platform and Node.js version? (For example Node.js 0.12 on Mac OS X)
    N/A
  3. Sample source code or steps to reproduce
    npm i json-schema-deref-sync@0.12

The most recent release has is tagged as 0.12.0, but released to npm as 0.13.0.

I ran a diff, the git and npm versions are very similar:

➜  json-schema-deref-sync git:(master) npm pack json-schema-deref-sync@0.13
➜  json-schema-deref-sync git:(master) ✗ tar -zxf json-schema-deref-sync-0.13.0.tgz 
➜  json-schema-deref-sync git:(master) ✗ diff package/lib/index.js lib/index.js 
252c252
<             newValue = _.merge(newValue, node)
---
>             newValue = _.merge({}, newValue, node)
➜  json-schema-deref-sync git:(master) ✗ diff package/lib/utils.js lib/utils.js 
➜  json-schema-deref-sync git:(master) ✗ diff package/lib/loaders/file.js lib/loaders/file.js 
➜  json-schema-deref-sync git:(master) ✗ diff package/package.json package.json              
13c13
<   "version": "0.13.0",
---
>   "version": "0.12.0",

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions