question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Prepare 1.0.0 release

See original GitHub issue

With the 1.0.0 release with Stryker we will make the following changes:

Preparation

Execution

  • Remove deprecated Factories from stryker-api.
  • Remove ES5 mutator
  • Set ‘javascript’ as the default mutator
  • Remove deprecated reporter config key
  • Remove deprecated project config key
  • Remove deprecated ‘default’ projectType for jest (in favor of ‘custom’)
  • Remove deprecated timeoutMs config key
  • Rename packages:
    • stryker => @stryker-mutator/core
    • stryker-xxx-yyy => @stryker-mutator/xxx-yyy
    • stryker-jasmine => @stryker-mutator/jasmine-framework
    • stryker-typescript => @stryker-mutator/typescript
  • Remove config key from being injectable
  • Remove getLogger and setImplementation from stryker-api/logging
  • Remove all deprecated apis/messages/etc
  • Update plugin loader to load plugins from @stryker-mutator (instead of stryker-)
  • Enable lerna versioning mode (not independent, other one)
  • Update stryker-cli to install @stryker-mutator/core instead of stryker and stryker-api
  • Update package.json keywords to @stryker-mutator/
  • Update keyword plugin to ‘stryker-mutator-plugin’

Clean up

This original post will be kept up-to-date.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:13 (13 by maintainers)

github_iconTop GitHub Comments

1reaction
simondelcommented, Mar 29, 2019

Since we released it, let’s close this 😃

1reaction
simondelcommented, May 23, 2018

What about renaming the reporter property of the stryker config to reporters? It’s an array after all. We could already implement this with a deprecation warning for people still using the property reporter and remove the reporter property in 1.0.0

Read more comments on GitHub >

github_iconTop Results From Across the Web

Prepare 1.0.0 release · Issue #285 · WordPress/performance
This issue is to track preparation of the upcoming 1.0.0 release up until publishing, which is due April 18, 2022.
Read more >
Prepare 1.0.0 release (!210) · Merge requests · CP3-CMS / bamboo ...
@swertz and I agreed to make a 1.0.0 release once !186 (merged) is merged. With these changes I can build a source distribution...
Read more >
SystemML Release Creation Process - SystemML 1.0.0
Step 1: Prepare the release. # Extract latest code to a directory <GitRepoHome> # Go to dev/release directory cd <GitRepoHome>/dev/release. 1.a ...
Read more >
Release Notes 1.0.0 | NGINX Service Mesh
These release notes provide general information and describe known issues for NGINX Service Mesh version 1.0.0, in the following categories:.
Read more >
Prepare and roll out a release - Play Console Help
Note: Apps created before August 2021 can use app bundles or APKs in releases. To learn more about why you would upload ReTrace...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found