Comments (17)
👍
from grunt-release.
👍
from grunt-release.
👍
from grunt-release.
I could really use the ability to run some custom tasks too. Here's my use case:
I'm publishing a built subfolder, which I need to copy the package.json file in to. If I copy the file before grunt-release runs, then the version number is old. Would be great to run a copy taste between bump and publish.
from grunt-release.
Well, this repo doesn't seem to be maintained anymore...
from grunt-release.
@ngryman you're welcome to fork or use something else.
from grunt-release.
Yeah I would love to see some options like:
{
preReleaseTasks: [],
postReleaseTasks: []
}
that will be arrays of grunt tasks that you want to run before and after the release grunt task begins. I can work on adding this in in the next week or so if @geddski is okay with it.
from grunt-release.
@mkay581 totally
from grunt-release.
@mkay581 Hey, could you find the time and work on this? Would be perfect to have it in before we land a major version.
from grunt-release.
ah my apologies. I ended up getting tied up around the time I responded to this and slipped my mind. I'll take a look later this evening after work and see if I can pull something together and open a pull
from grunt-release.
No worries. Just check back when you're done. If anyone else works on it, they will post here I guess :)
from grunt-release.
working on it now... is there a way to denote issues that are "in progress" in your setup? To prevent others from working on the same thing?
from grunt-release.
Hi, there seems to be an issue with this code:
return function () {
var method = map[taskName],
tasks = options[method];
if (tasks.length) {
grunt.log.ok('running ' + method + ' ');
if (!nowrite) {
grunt.task.run(tasks);
}
}
}
It doesn't return a promise, so
.then(ifEnabled('beforeBumpTasks', runTasks('beforeBump')))
.then(ifEnabled('bump', bump))
.then(ifEnabled('afterBumpTasks', runTasks('afterBump')))
.then(ifEnabled('beforeReleaseTasks', runTasks('beforeRelease')))
doesn't work as expected. I just released a package and my afterBumpTasks
finished after the release
task finished:
$ grunt release
Running "release" task
>> bumped version of bower.json to 1.7.2
>> bumped version of package.json to 1.7.2
>> running afterBumpTasks
>> staged bower.json package.json
>> Committed all files
>> created new git tag: v1.7.2
>> pushed to remote
>> pushed new tag 1.7.2 to remote
>> published version 1.7.2 to npm
>> created v1.7.2 release on github.
Running "less:dist" (less) task
File build/shariff.complete.css created
Running "browserify:dist_complete_min" (browserify) task
Running "browserify:dist_min" (browserify) task
There also seems to be an issue with the custom tasks docs:
afterBump: [], // optional grunt tasks to run after file versions are bumped`
Using afterBump
doesn't work, but afterBumpTasks
does.
from grunt-release.
yeah you're right, I think there was a mixup with the documentation. i'll open a pull request with change. thanks for pointing that out @pmb0
from grunt-release.
@pmb0 pull request created here: #105. Let me know if this is what you were thinking.
from grunt-release.
Thank you @mkay581! I think that is the fix. Looking forward to the patch. :)
from grunt-release.
This is done now, I guess.
beforeBump: [], // optional grunt tasks to run before file versions are bumped
afterBump: [], // optional grunt tasks to run after file versions are bumped
beforeRelease: [], // optional grunt tasks to run after release version is bumped up but before release is packaged
afterRelease: [], // optional grunt tasks to run after release is packaged
If there are any other issues, please open another issue :)
from grunt-release.
Related Issues (20)
- grunt-release should quit if any of the additional tasks (i.e.: beforeBump) fail HOT 4
- Info on *.zip release on github
- Committing files generated by `beforeBump` task HOT 5
- Changelog md not being updated with commits HOT 3
- Should work with targets
- [Question] Is there a way to add additonal files to commit? HOT 3
- how to push using package repository
- runTasks (beforeRelease, afterRelease, etc.) ignores --gruntfile and --base
- Not pushing modified package.json to github HOT 1
- Dead Project HOT 11
- Dependencies out of date
- Add gitlab support
- Chaining beforeBump, afterBump, beforeRelease and afterRelease does not work HOT 3
- Generating hotfix tag
- Version bump does not update package-lock.json HOT 1
- Npm Release HOT 1
- Unhelpful output when `npm publish` fails
- Continue after failure
- Add some way to support 2-factor for npm
- How, specifically, do you add an alphanumeric identifier like "alpha" or "beta"? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from grunt-release.