I'm currently trying to setup semantic-release to publish package.json with the updated version and CHANGELOG to both npm and GitHub. From what I've read, this seem possible using #semantic-release/git and #semantic-release/changelog plugins. However, I couldn't make it work with my configs. My package is something like that: (source # redux-form-input-masks)
(...)
"devDependencies": {
"#semantic-release/changelog": "^1.0.1",
"#semantic-release/git": "^3.0.1",
"semantic-release": "^13.4.1",
(...)
},
"release": {
"debug": true,
"verifyConditions": [
"#semantic-release/changelog",
"#semantic-release/npm",
"#semantic-release/git",
"#semantic-release/github"
],
"prepare": [
"#semantic-release/changelog",
"#semantic-release/npm",
{
"path": "#semantic-release/git",
"assets": [
"package.json",
"CHANGELOG.md"
],
"message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
}
],
"publish": [
"#semantic-release/npm",
"#semantic-release/github"
]
}
(...)
And the Travis CI build log shows:
[0Ktravis_fold:start:after_success.2
[0Ktravis_time:start:0014f334
[0K$ npx semantic-release
[Semantic release]: Running semantic-release version 13.4.1
[Semantic release]: Load plugin verifyConditions from #semantic-release/changelog
[Semantic release]: Load plugin verifyConditions from #semantic-release/npm
[Semantic release]: Load plugin verifyConditions from #semantic-release/git
[Semantic release]: Load plugin verifyConditions from #semantic-release/github
[Semantic release]: Load plugin analyzeCommits from #semantic-release/commit-analyzer
[Semantic release]: Load plugin generateNotes from #semantic-release/release-notes-generator
[Semantic release]: Load plugin publish from #semantic-release/npm
[Semantic release]: Load plugin publish from #semantic-release/github
[Semantic release]: Run automated release from branch master
[Semantic release]: Call plugin verify-conditions
[Semantic release]: Verify authentication for registry https://registry.npmjs.org/
[Semantic release]: Wrote NPM_TOKEN to .npmrc.
[Semantic release]: Verify GitHub authentication
[Semantic release]: Found git tag v0.3.5 associated with version 0.3.5
[Semantic release]: Found 1 commits since last release
[Semantic release]: Call plugin analyze-commits
[Semantic release]: Analyzing commit: fix: testing semantic-release
[Semantic release]: The release type for the commit is patch
[Semantic release]: Analysis of 1 commits complete: patch release
[Semantic release]: The next release version is 0.3.6
[Semantic release]: Call plugin verify-release
[Semantic release]: Call plugin generateNotes
[Semantic release]: Create tag v0.3.6
[Semantic release]: Call plugin publish
[Semantic release]: Wrote version 0.3.6 to package.json
[Semantic release]: Wrote version 0.3.6 to package-lock.json
[Semantic release]: Publishing version 0.3.6 to npm registry
+ redux-form-input-masks#0.3.6[Semantic release]: Published GitHub release: https://github.com/renato-bohler/redux-form-input-masks/releases/tag/v0.3.6
[Semantic release]: Published release: 0.3.6
travis_time:end:0014f334:start=1519095849162192955,finish=1519095858417255129,duration=9255062174
[0Ktravis_fold:end:after_success.2
This does publish a new tag and release on both GitHub and npm, but it doesn't create a CHANGELOG.md (as I'm expecting from changelog plugin) and it doesn't commit the package.json with the updated version (0.3.6 in this case - as I'm expecting from git plugin).
Am I missing something?
I've finally made it work.
The problem was that npm i #semantic-release/git --save-dev would install the git plugin at version 3.0.1, and I was reading the API for for version 4.0.0.
To solve it, I did
npm i --save-dev semantic-release#15 #semantic-release/git#4 #semantic-release/changelog#2
Related
When integrating react-native-firebase within my native app, I am facing following error while launching the application
Module build failed (from ./node_modules/babel-loader/lib/index.js):
TypeError: this.getOptions is not a function
at Object.loader (/Users/nikhilfarheen/Documents/ReactComponent/sharespecs/node_modules/babel-loader/lib/index.js:46:28)
at Object.<anonymous> (/Users/nikhilfarheen/Documents/ReactComponent/sharespecs/node_modules/babel-loader/lib/index.js:41:12)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
packages installed are
"dependencies": {
"#babel/plugin-transform-react-jsx": "^7.20.7",
"#react-native-firebase/app": "^16.5.0",
"#react-native-firebase/messaging": "^16.5.0",
"babel": "^6.23.0",
"babel-core": "^6.26.3",
"babel-loader": "^9.1.2",
"firebase": "^9.15.0",
"link": "^1.5.1",
"react-native": "^0.71.0",
"react-native-cli": "^2.0.1",
"react-native-device-info": "^10.3.0",
"style-loader": "2.0.0",
"webpack-stream": "^7.0.0"
}
Tried installing peer dependencies of other packages like webpack but nothing worked
You have missed downloading dependencies.
Follow below steps to install dependencies mentioned in their official doc
Run npm uninstall babel-loader
Run npm install -D babel-loader #babel/core #babel/preset-env webpack
Please help. Git repo to Vercel build failed.
I did this a few weeks ago, and now it's suddenly failing.
This is the error I'm getting:
[16:51:16.832] Cloning github.com/benjanknoetze/benjan-spot (Branch: master, Commit: 1a2ddf0)
[16:51:20.725] Cloning completed: 3.893s
[16:51:21.708] Looking up build cache...
[16:51:21.989] Build Cache not found
[16:51:22.220] Running "vercel build"
[16:51:22.720] Vercel CLI 28.2.0
[16:51:22.981] Your application is being built using `next build`. If you need to define a different build step, please create a `vercel-build` script in your `package.json` (e.g. `{ "scripts": { "vercel-build": "npm run prepare && next build" } }`).
[16:51:22.983] Installing dependencies...
[16:51:23.313] yarn install v1.22.17
[16:51:23.323] warning package.json: No license field
[16:51:23.329] info No lockfile found.
[16:51:23.332] warning No license field
[16:51:23.333] [1/4] Resolving packages...
[16:51:23.334] [2/4] Fetching packages...
[16:51:23.335] [3/4] Linking dependencies...
[16:51:23.339] [4/4] Building fresh packages...
[16:51:23.342] success Saved lockfile.
[16:51:23.344] Done in 0.04s.
[16:51:23.355] Warning: Could not identify Next.js version, ensure it is defined as a project dependency.
[16:51:23.355] Error! No Next.js version could be detected in your project. Make sure `"next"` is installed in "dependencies" or "devDependencies"
My packgage.json:
Error message 1
When I run my NextJs program this error always pops up
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist#latest --update-db
So then I run npx browserslist#latest --update-db in the shell:
npx: installed 6 in 1.905s
Current version: 1.0.30001179
New version: 1.0.30001179
Removing old caniuse-lite from lock file
Installing new caniuse-lite version
$ npm install caniuse-lite
Cleaning package.json dependencies from caniuse-lite
$ npm uninstall caniuse-lite
caniuse-lite has been successfully updated
No target browser changes
And the I when I run my Next program again, the same error occurs. This started happening to me yesterday. I just used npx create-next-app and the npm run dev.
UPDATE
The new version (10.0.6) has been released few moments ago. No warnings present.
This is a falsy warning in current Next.js version (10.0.5).
It's already solved in canary version, which is a base for the next stable version. You can install it (npm install next#canary or yarn add next#canary) and make sure there are no warnings.
Since canary version is not recommended for using in production, you can continue working in 10.0.5 without any side effects. The warning will disappear after new stable version release.
I am new to laravel and i am stuck into the error from last few days, I had cloned laravel project from gitlab and want to run this on localhost i have php7.2, laravel 5.3,ubuntu 18.10 but when i tried to run "composer install" on terminal inside project directory i.e /var/www/html/project_name/ it generates an error while installation.
priyanka#desktop:/var/www/html/project_name$ composer install
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Package operations: 89 installs, 0 updates, 0 removals
- Installing aspose/cloud-sdk-php (1.1.1): Downloading (0%) Failed to download aspose/cloud-sdk-php from dist: The "https://codeload.github.com/asposeforcloud/Aspose_Cloud_SDK_For_PHP/legacy.zip/abf381316d109316f995d6a9f2c46d83357dd5a8" file could not be downloaded (HTTP/1.1 404 Not Found)
Now trying to download from source
Installing aspose/cloud-sdk-php (1.1.1): Cloning abf381316d from cache
abf381316d109316f995d6a9f2c46d83357dd5a8 is gone (history was rewritten?)
[RuntimeException]
Failed to execute git checkout 'abf381316d109316f995d6a9f2c46d83357dd5a8' -
&& git reset --hard 'abf381316d109316f995d6a9f2c46d83357dd5a8' --
fatal: reference is not a tree: abf381316d109316f995d6a9f2c46d83357dd5a8
install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--] []...
I've tried the following solutions which i found from different sites
composer update
composer update --no-scripts
composer install --no-scripts
sudo apt install zip unzip php7.2-zip
composer dump-autoload
enter image description here
I just cloned my meteor github repo to a new machine and now I have to npm install some packages again. I thought that they are part of the meteor app once I have them installed. (and I checked. they are in the node_modules folder and listed in the packages.json). Nonetheless, I get the error:
Can't find npm module 'react'. Did you forget to call 'Npm.depends' in package.js witin the 'modules-runtime'package?
I am running meteor 1.3.1