Skip to content

Commit

Permalink
Release 6.0.3
Browse files Browse the repository at this point in the history
  • Loading branch information
@charlierudolph
charlierudolph committed Oct 27, 2019
1 parent 086ba83 commit a89eae3
Show file tree
Hide file tree
Showing 3 changed files with 200 additions and 26 deletions.
6 changes: 5 additions & 1 deletion CHANGELOG.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,10 @@ Please see [CONTRIBUTING.md](https:/cucumber/cucumber/blob/master/CO

### [Unreleased](https:/cucumber/cucumber-js/compare/v6.0.2...master) (In Git)

### [6.0.3](https:/cucumber/cucumber-js/compare/v6.0.2...v6.0.3) (2019-10-27)

* Revert JSON formatter changes to be backward compatible

### [6.0.2](https:/cucumber/cucumber-js/compare/v6.0.1...v6.0.2) (2019-10-07)

* Upgrade to cucumber-expressions 8.0.1 to fix failure on multiple installs
Expand All @@ -15,7 +19,7 @@ Please see [CONTRIBUTING.md](https:/cucumber/cucumber/blob/master/CO
#### BREAKING CHANGES

* Drop support for Node.js 6
* JSON formatter has major breaking changes. View some sample outputs [here](/features/fixtures/formatters/). The `*.json.js` files contain the js objects the json parses to.
* JSON formatter has major breaking changes. View some sample outputs [here](/features/fixtures/formatters/). The `*.json.js` files contain the js objects the json parses to. (UPDATE - reverted in 6.0.3)
* Duration is now in nanoseconds in event-protocol formatter and in events sent to custom formatters
* Custom formatters: Formatter helpers and EventDataCollector had breaking changes to support retry

Expand Down
218 changes: 194 additions & 24 deletions dist/cucumber.js
View file

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion package.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
"gherkin",
"tests"
],
"version": "6.0.2",
"version": "6.0.3",
"homepage": "http:/cucumber/cucumber-js",
"author": "Julien Biezemans <[email protected]> (http://jbpros.net)",
"contributors": [
Expand Down

3 comments on commit a89eae3

@Carmot
Copy link

@Carmot Carmot commented on a89eae3 Oct 31, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @charlierudolph ,

First of all, thanks for your work on cucumber-js. We've been using it for three years now and we are very happy.
Just wanted to ask you something, we have it integrated in our CI/CD system and we reading tests result file to show a report to the high level user of how tests have gone.

We updated our script to read the latest format after version 6 was release, but now within the same version the format has been reverted back to previous, no problem, we got old script version from git and running again.

I'd like to know what is the expected roadmap for this, I mean, are you considering moving to new format in some of the next releases or are you planning to stay on with this format?

Thank you!

@aslakhellesoy
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @Carmot.

Our plan is to deprecate the json formatter in version Cucumber.js version 7 and encourage users to migrate to a new machine-readable format for results based on cucumber-messages. This output will be generated by a new protobuf formatter which we'll add to all Cucumber implementations.

We then aim to remove the json formatter in Cucumber.js version 8. People who have not upgraded their tooling to use the new protobuf formatter by then will still be able to convert output from the protobuf formatter to JSON using the new standalone JSON formatter which is available as an executable (it's a command line tool written in go).

@aslakhellesoy
Copy link
Contributor

@aslakhellesoy aslakhellesoy commented on a89eae3 Oct 31, 2019 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've written this up in two issues:

Let's continue the discussion there as discussions in commits easily fall off the radar.

Please sign in to comment.