v6.1.0

[tvdeyen]

Features

• Add page layouts repository class option #2410 (tvdeyen)
• Add element definitions repository class option #2409 (tvdeyen)
• Allow to set preview_sources #2407 (tvdeyen)
• Allow to add anchors to ingredients #2395 (tvdeyen)
• Add a error logger exception handler #2387 (tvdeyen)
• Add a element DOM id class #2373 (tvdeyen)

Changes

• Remove old jasmine based javascript specs #2400 (tvdeyen)
• Update bundled Tinymce to 4.9.11 #2399 (tvdeyen)
• Add Headline size and level selects as input addons #2398 (tvdeyen)
• Remove Element.available scope #2372 (tvdeyen)
• Remove element_dom_id helper #2369 (tvdeyen)
• Use position for element dom_id #2368 (tvdeyen)
• Disallow deleting pages if still attached to menu node #2338 (afdev82)

Fixes

• Add :contact_form_id to messages params in messages_controller #2403 (chiperific)
• Do not create thumbs for invalid pictures #2386 (tvdeyen)

Misc

• [ruby - main] Upgrade sqlite3 to version 1.6.0 #2408 (depfu)
• [ruby - main] Upgrade puma to version 6.0.1 #2404 (depfu)
• CI: Update brakeman scan #2390 (tvdeyen)
• [ruby - main] Upgrade net-imap to version 0.3.1 #2379 (depfu)
• CI: Try ubuntu-latest #2378 (tvdeyen)
• [ruby - main] Upgrade sqlite3 to version 1.5.0 #2374 (depfu)
• [js] Upgrade babel-jest to version 29.0.1 #2362 (depfu)
• Use released Rails gems again for local testing #2355 (tvdeyen)
• [js] Upgrade babel-jest to version 28.0.2 #2324 (depfu)

New Contributors

• @pascalbetz made their first contribution in Update published_at only after page has been published. #2331
• @chiperific made their first contribution in Add :contact_form_id to messages params in messages_controller #2403

🙌🏻 thanks ❤️

Full Changelog: v6.0.0...v6.1.0

---

This discussion was created from the release v6.1.0.

[tvdeyen]

This will be (most likely) the final release for the v6 release branch.

In 7.0 we will remove Essence classes, since they have been deprecated since 6.0 and have a much better replacement with Ingredients.

So, please update your sites to use ingredients instead of essences.

[tvdeyen]

I added a guide to update essences to ingredients #2413

[afdev82]

Is the project using semantic versioning or not?
I have a problem in production (error 500) because of the Element.available scope being removed between v6.0.12 and v6.1.0.
The deprecation was not even added to v6.0.12, but only in v6.1.0-a (tvdeyen@1260fd7)
Also the deprecation for the element_dom_id helper removed in v6.1.0 was added in v6.0.10.
I've expected that such breaking changes to appear in a major version, not a minor version.
Am I wrong or am I missing something about that?
Thank you for your support.

[tvdeyen]

Is the project using semantic versioning or not?

No. Like Rails, we do not follow semver, but we try to avoid breaking changes like this in minor version wherever possible.

I have a problem in production (error 500) because of the Element.available scope being removed between v6.0.12 and v6.1.0.
The deprecation was not even added to v6.0.12, but only in v6.1.0-a (tvdeyen@1260fd7)
Also the deprecation for the element_dom_id helper removed in v6.1.0 was added in v6.0.10.

Why do you have an error in production? Not sure how you do deployment, but this seems wrong. Anyhow, the removal should only have happened in 7.0. I can release a new version that re-introduces the available scope and the element_dom_id helper in a new 6.1 release.

I've expected that such breaking changes to appear in a major version, not a minor version.
Am I wrong or am I missing something about that?

Again, we never said that we follow semver, but I can relate to that disappointment and we will release a new version that fixes that.

Thank you for your support.

Thanks for bringing this to our attention.

[afdev82]

Ok...
Well, in the Alchemy Guides I read that: https://guides.alchemy-cms.com/upgrading.html#major-version-upgrades
And here too: https://github.com/AlchemyCMS/alchemy_cms#-releasing

Why do you have an error in production? Not sure how you do deployment, but this seems wrong. Anyhow, the removal should only have happened in 7.0. I can release a new version that re-introduces the available scope and the element_dom_id helper in a new 6.1 release.

I had the error in the homepage because the "available" scope was used there and it was removed after the update to v6.1.0.
I've fixed the problem now, but maybe it could help someone else.