thebruce / semverist Goto Github PK
View Code? Open in Web Editor NEWSemver Inspection and Utilities for Semver Object and Directory hierarchies
License: Apache License 2.0
Semver Inspection and Utilities for Semver Object and Directory hierarchies
License: Apache License 2.0
Branch |
Build failing |
---|---|
Dependency | semver |
Current Version | 5.4.1 |
Type | dependency |
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.
The new version differs by 7 commits.
44cbc84
v5.5.0
1d37529
Cleaned up coerce behavior
e7092b4
Improved coerce regex and added coerce to README.
68cef2d
Added version coercion to the module and CLI.
ec6f97a
range.bnf: Fix invalid bracket expression
906b664
travis: don't cache node_modules
7184ff4
range.bnf: Remove unnecessary empty entry
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
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.
2.1.7
to 2.1.8
.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.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot
To Reproduce:
test
test
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.
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:
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.
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.
Branch |
Build failing |
---|---|
Dependency | molotov |
Current Version | 1.1.1 |
Type | dependency |
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.
<a name"1.2.0">
The new version differs by 5 commits.
c428397
Merge pull request #54 from thebruce/dynamicPlugs
da85903
fix(travis): Removed node 4.
6b10069
feat(dynamicPlugs): Added dynamicPlugin signature to molotov.js implementation example in docs.
203ff6a
fix(lint): Maxlen for comments in mixinpluginmaker fixed.
ad08884
'feat(dynamicPlugs): Added the ability to have dynamic plugins passed in poltopullo.resolve(dynamicPlugs)'
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot
Branch |
Build failing |
---|---|
Dependency | eslint-plugin-import |
Current Version | 2.3.0 |
Type | devDependency |
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
The new version differs by 10 commits.
44ca158
update utils changelog
a3728d7
bump eslint-module-utils to v2.1.0
3e29169
bump v2.4.0
ea9c92c
Merge pull request #737 from kevin940726/master
8f9b403
fix typos, enforce type of array of strings in allow option
95315e0
update CHANGELOG.md
28e1623
eslint-module-utils: filePath in parserOptions (#840)
2f690b4
update CI to build on Node 6+7 (#846)
7d41745
write doc, add two more tests
dedfb11
add allow glob for rule no-unassigned-import, fix #671
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot
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:
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.
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.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.