parallel-js/parallel.js

Release new version?

jdb8 opened this issue · 12 comments

jdb8 commented

Prerequisites

  • Using yarn
  • Using an up-to-date master branch
  • Using latest version of devtools. See wiki for howto update
  • Link to stacktrace in a Gist (for bugs)
  • For issue in production release, devtools output of DEBUG_PROD=true yarn build && yarn start
  • Tried solutions mentioned in #400

Expected Behavior

The version available on npm should be the same as the version on github master.

Current Behavior

The version on npm is 0.2.1 while the package.json on master is 0.3.0: https://www.npmjs.com/package/paralleljs vs

parallel.js/package.json

Line 3 in 5fe4970

"version": "0.3.0",

Possible Solution

Release 0.3.0 on npm. Even better would be to release a v0.2.2 which fixes the issue outlined below (this commit).

Steps to Reproduce (for bugs)

N/A

Context

There's a specific issue with v0.2.1 which is the zero-width spaces present in the package.json. This was fixed in this commit but hasn't been released yet. It means that packages depending on paralleljs are pulling in a broken package.json, which breaks some tooling that tries to parse package.json files inside node_modules.

Your Environment

  • Node version : any
  • Version or Branch used : v0.2.1
  • Operating System and version : any
  • Link to your project : n/a
mathiasrw commented

Good point. Lets get it flying.

stale commented

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

jdb8 commented

Any update on this?

  • 👍1
stale commented

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

jdb8 commented

Bump - @mathiasrw, not sure if you have access to release a new version, but this would still be useful.

mathiasrw commented

@jdb8 Let me see what I can do.

mathiasrw commented

@adambom @Sebmaster @MaXFalstein @amilajack @vikr01

Any objections to releasing the current version?

stale commented

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

mathiasrw commented

@adambom @Sebmaster @MaXFalstein @amilajack @vikr01

I am intending to release a new version npm if I hear nothing from you.

amilajack commented

There is actually no new version. I reverted that work because it makes too many breaking changes.

jdb8 commented

@amilajack to clarify: e1b71c0 was reverted? The only reason I personally wanted a new version was because the version that's latest on npm has a broken package.json, which breaks some tooling. It's fine (and actually preferable) if the next release is a patch 0.2.2 which solely includes that commit.

amilajack commented

@mathiasrw pushed some changes and fixes. Would love if you could bump package to 0.3.0. I dont have publishing permission.

@jdb8 After publishing a new version, it should work