-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency grunt to v1 - autoclosed #125
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mend-for-github-com
bot
changed the title
Update dependency grunt to v1
Update dependency grunt to v1 - autoclosed
Nov 20, 2024
mend-for-github-com
bot
changed the title
Update dependency grunt to v1 - autoclosed
Update dependency grunt to v1
Nov 20, 2024
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/grunt-1.x
branch
from
November 20, 2024 18:18
a38a62a
to
2d9afa7
Compare
mend-for-github-com
bot
changed the title
Update dependency grunt to v1
Update dependency grunt to v1 - autoclosed
Nov 21, 2024
mend-for-github-com
bot
changed the title
Update dependency grunt to v1 - autoclosed
Update dependency grunt to v1
Nov 21, 2024
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/grunt-1.x
branch
from
November 21, 2024 18:13
2d9afa7
to
776a725
Compare
mend-for-github-com
bot
changed the title
Update dependency grunt to v1
Update dependency grunt to v1 - autoclosed
Nov 23, 2024
mend-for-github-com
bot
changed the title
Update dependency grunt to v1 - autoclosed
Update dependency grunt to v1
Nov 23, 2024
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/grunt-1.x
branch
from
November 23, 2024 00:19
776a725
to
5d30ab8
Compare
mend-for-github-com
bot
changed the title
Update dependency grunt to v1
Update dependency grunt to v1 - autoclosed
Nov 25, 2024
mend-for-github-com
bot
changed the title
Update dependency grunt to v1 - autoclosed
Update dependency grunt to v1
Nov 25, 2024
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/grunt-1.x
branch
from
November 25, 2024 02:06
5d30ab8
to
9943334
Compare
mend-for-github-com
bot
changed the title
Update dependency grunt to v1
Update dependency grunt to v1 - autoclosed
Dec 4, 2024
mend-for-github-com
bot
changed the title
Update dependency grunt to v1 - autoclosed
Update dependency grunt to v1
Dec 4, 2024
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/grunt-1.x
branch
from
December 4, 2024 18:14
9943334
to
a794983
Compare
mend-for-github-com
bot
changed the title
Update dependency grunt to v1
Update dependency grunt to v1 - autoclosed
Dec 17, 2024
mend-for-github-com
bot
changed the title
Update dependency grunt to v1 - autoclosed
Update dependency grunt to v1
Dec 17, 2024
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/grunt-1.x
branch
from
December 17, 2024 00:16
a794983
to
5036da8
Compare
mend-for-github-com
bot
changed the title
Update dependency grunt to v1
Update dependency grunt to v1 - autoclosed
Dec 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.1.0
->1.5.3
By merging this PR, the issue #89 will be automatically resolved and closed:
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Release Notes
gruntjs/grunt (grunt)
v1.5.3
Compare Source
572d79b
58016ff
0749e1d
69b7c50
v1.5.2
Compare Source
7f15fd5
b0ec6e1
433f91b
v1.5.1
Compare Source
ad22608
0652305
v1.5.0
Compare Source
b2b2c2b
3eda6ae
47d32de
2e9161c
04b960e
aad3d45
fdc7056
e35fe54
v1.4.1
Compare Source
e7625e5
5d67e34
d13bf88
08896ae
eee0673
1b6e288
v1.4.0
Compare Source
63b2e89
106ed17
49de70b
47cf8b6
e86db1c
4952368
v1.3.0
Compare Source
faab6be
520fedb
7e669ac
safeLoad
for loading YML files viafile.readYAML
.e350cea
7125f49
00d5907
v1.2.1
Compare Source
ae11839
9d23cb6
e789b1f
v1.2.0
Compare Source
is visible to Node.js and NPM, instead of node_modules directly
inside package that have a dev dependency to these pluginhttps://github.com/gruntjs/grunt/pull/1677nt/pull/1677)
coffeescript is still around, Grunt will attempt to load it.
If it is not, and the user loads a CoffeeScript file,
Grunt will print a useful error indicating that the
coffeescript package should be installed as a dev dependency.
This is considerably more user-friendly than dropping the require entirely,
but doing so is feasible with the latest grunt-cli as users
may simply use grunt --require https://github.com/gruntjs/grunt/pull/1675thub.com/Remove coffeescript from dependencies. gruntjs/grunt#1675)
(https://github.com/gruntjs/grunt/pull/15701570)
(https://github.com/gruntjs/grunt/pull/16971697)
v1.1.0
Compare Source
v1.0.4
Compare Source
v1.0.3
Compare Source
v1.0.2
Compare Source
v1.0.1
Compare Source
v1.0.0
Compare Source
v0.4.5
Compare Source
v0.4.4
Compare Source
v0.4.3
Compare Source
v0.4.2
Compare Source
v0.4.1
Compare Source