🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As nunjucks is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Fix handling methods and attributes of static arrays, objects and primitives. Solves the issue #937
Add support for python-style array slices with Jinja compat enabled. Fixes #188; merge of #976.
Fix call blocks having access to their parent scope. Fixes #906; merge of #994.
Fix a bug that caused capturing block tags (e.g. set/endset, filter/endfilter) to write to the global buffer rather than capturing their contents. Fixes #914 and #972; merge of #990. Thanks Noah Lange.
The new version differs by 28 commits (ahead by 28, behind by 1).
Hello lovely humans,
nunjucks just published its new version 3.0.1.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As nunjucks is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
The new version differs by 28 commits (ahead by 28, behind by 1).
8262f45
Release 3.0.1
efd2ee9
Merge pull request #994 from mozilla/fix-call-scope
3fb9e9f
Allow {% call %} blocks to access parent scope. Fixes #906
5c2bf56
Merge pull request #908 from forresst/update-docs-in-french-5
a2c3908
Merge pull request #953 from AndyWendt/patch-1
5312e66
Merge pull request #990 from noahlange/914-macro-set-block
04b0fb5
Addresses 914; capture blocks in macros now write to proper tmp buffer.
be0cfec
Merge pull request #976 from theatlantic/pr/slice-support-jinja-compat
f44646b
Nunjucks now has a maintainer; remove msg in README saying otherwise
9af75a5
Update CONTRIBUTING.md
18ba686
Update README.md
5ef361d
Update README.md
1372175
Add python slice support to jinja-compat. fixes #188
1595bc5
Indent jinja-compat.js to four spaces for consistency
5362038
Fix missing
}}
in templating.mdThere are 28 commits in total. See the full diff.