Making another release
See original GitHub issueBefore Lektor 3 I had trouble with adding custom attachment types. Since it seemed to be fixed in master
I just patched the file myself. After updating I got the error and investigated a bit more.
The patch in question is PR #252 (which fixes my issue). It was merged in October 2016, way before this release. Looking at environment.py
in master
confirms that the fix is indeed there (and the blame confirms it hasn’t been modified since the PR).
I’ve downloaded both the wheel and tarball from PyPI for Lektor 3.0.1 (uploaded June 2017) and none of them contain the fix in environment.py
.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
How to Pick a Release Date [2022 Guide] - Other Record Labels
5 things to consider when you pick a release date. ; Consider the margin… Allow one to two months before and after your...
Read more >Start a release from another release - XebiaLabs documentation
In the “master release” scenario, one release starts several “subreleases” and then waits for them to finish. A Create Release task starts each...
Read more >Is it possible to trigger a release with another release in VSTS?
If you create a schedule for the release of each of your application repositories you ... Another option is to use stage scheduled...
Read more >The Elder Scrolls 6: Everything we know so far - GamesRadar
The Elder Scrolls 6 is coming, but it's behind another of the upcoming Bethesda games in the release schedule queue. The studio is...
Read more >Jumanji 4 potential release date, cast and more - Digital Spy
But I hope they make another one because it's so much fun," Gillan told Collider in July 2021. Kevin Hart, Dwayne Johnson, Karen...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve just tagged 3.1.0.dev1 and pushed it to PyPI. Anyone please feel free to play with it with
pip install lektor==3.1.0.dev1
. If all goes well I want to cut 3.1 as a real release later this month.After much ado, Lektor 3.1 is now released. Going forward, now that that backlog is gone, I intend on making incremental releases more frequently.