thebruce / semverist Goto Github PK

Version 5.5.0 of semver was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semver is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Right now object and directory writing occur synchronously and are blocking. Let's support both sync and async writing. This will change the api and schoenberg as well as manifest/composer.

We have config and processed results files for tests we can use them in our docs.

Klaw sync has changed how the exception patterns are factored in. This has an impact on config. We need to establish a new pattern to exclude or include files, reg ex is probably best here.

The dependency molotov was updated from 2.1.7 to 2.1.8.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

molotov is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

To Reproduce:

1. Create semverist config with groups set to false. Add a group anyway and add a member of that group as test
2. Create a semverish shape with only one named attribute in it test
3. Create composer with that config and shape.
4. See that semver realizations are there appropriately but no attribute of test has been realized.

Right now the plugin chain runs object Writing into directory writing. It would be useful from a transformation perspective to not tie those two together but rather to tie the idea of publishing (writing to a directory or making an object immutable) together. That way as much transformation as possible can be delegated to the user and we only have to worry about json writing specifically as a convenience. This would support users getting and transforming the composition once read into a semverist object transforming it to what ever they want and either using the default extension in config or the extant configuration as indications of what the file extension should be.

Need to simplify composition calls and then document.

We are close but not there yet.

Need to ensure that lazy semver handling works for the converter object and it takes that behavior into account in its ranges.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Right now JSON is enforced by having a to json converter on input - if we abstract this out a little bit we should have it read in all files as default or specify json converter (for convenience). Mostly we'd delegate to reading in the contents of the file and then having consumers manipulate that content at the manifest level.

If config passed into schoenberg has semverist.molotov key - this has been passed in to override some options within the molotov plugin loader for semverist, such as plugins or supers. Check if this is set and if it is merge over the default values from semverist. If nothing is passed in though - use the defaults.

This would be in the init or more likely setSemverishObject with a super call up.

Limit the semver realizations based on a config range - to prevent writing realizations to different configs.

Prerelease adjacency is currently out of whack, 0-alpha.0 and 0-alpha.1 with the same elements will produce odd behavior with the converter object reporting that 0-alpha.1 is a child of 0-alpha.0.

Additionally 0-alpha.0 and 0-beta.1 can have odd adjacency results.

Not the best that we dropped, let's get it back to 💯

Need others than assuming json. Could write file and provide capability to specify extension.

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.2.0 of molotov was just published.

This version is covered by your current version range and after updating it in your project the build failed.

molotov is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Version 2.4.0 of eslint-plugin-import just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-import is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

It is one big terrifying regEx, let us smallenize it.