Added deprecations page for Cohesivo 6.0#3279
Conversation
Preview of modified filesPreview of modified Markdown: |
Summary
Errors per inputErrors in site/release_notes/cohesivo_v6.0_deprecations/index.html
Errors in site/resources/rector/index.html
Redirects per inputRedirects in site/release_notes/cohesivo_v6.0_deprecations/index.html |
mnocon
force-pushed
the
deprecations-page
branch
from
5e09d90 to
7e4904b
Compare
mnocon
force-pushed
the
deprecations-page
branch
from
7e4904b to
91b5768
Compare
bnowak
left a comment
bnowak
left a comment
There was a problem hiding this comment.
Shouldn't it be merged into the lowest version (4.6) and be merged-up to all higher versions? I don't know what rules do we have regarding documentation versioning?
|
|
||
| | Deprecated since | Entity | Change | | ||
| | --- |------------------------------------------------------------------------------------|-----------------------------------------------------------| | ||
| | v5.0.9 | [`SudoStamp`](background_tasks.md#sudostamp) | No longer attached automatically to every dispatched message. For messages that should be processed without taking permissions into account, always attach the SudoStamp manually. | |
There was a problem hiding this comment.
All other Entity table entries use Fully Qualified Class Names, this one is not. For consistency we could use its long version as well: \Ibexa\Contracts\Messenger\Stamp\SudoStamp.
| Add the Composer dependency: | ||
|
|
||
| ``` bash | ||
| composer require --dev ibexa/rector:[[= latest_tag_5_0 =]] |
There was a problem hiding this comment.
I wouldn't point it to any specific version, as that would lock/block any potential future updates of that package. If we leave only composer require --dev ibexa/rector - composer will install its latest available matching version. This way, the client will be able to update that package too with regular composer update 😉
konradoboza
left a comment
konradoboza
left a comment
There was a problem hiding this comment.
Looks good! Do we have a plan to make some more noise about this page to create a habit it should be checked from time to time for the new additions?
| vendor/bin/rector | ||
| ``` | ||
|
|
||
| ## Refactor JavaScipt code |
There was a problem hiding this comment.
I think it should be 'JavaScript' ;)
For versioning we don't use a flow based on git merges, instead we squash the commits into a single one when merging and then cherry-pick it manully to the appropriate versions. I know it's a bit unusual, but it works 😉 Suggestions applied in 1fda0e8, thank you!
Yes, the plan is to mention this page in every release notes when we add a new deprecation to this list, to raise awareness around it. |
ibexa-workflow-automation-1
Bot
requested review from
adriendupuis,
dabrt and
julitafalcondusza
and removed request for
a team
|
|
||
| As announced during Ibexa Summit 2026, [Ibexa DXP will be renamed to Cohesivo](https://www.ibexa.co/blog/redefining-the-dxp-from-execution-to-orchestration) to support the new [orchestration platform approach](https://www.ibexa.co/blog/the-orchestration-era). | ||
|
|
||
| To learn more about the new brand, visit the [Cohesivo official site](https://cohesivo.com). |
There was a problem hiding this comment.
Discussed the sentences above with Kamil - it's ok, and improvements to the cohesivo.com site will be released on 16.06 (2 days before the next planned release when I'd like to merge this)
julitafalcondusza
left a comment
julitafalcondusza
left a comment
There was a problem hiding this comment.
Please check my comments.
Co-authored-by: julitafalcondusza <117284672+julitafalcondusza@users.noreply.github.com>
6 participants
Target: 4.6, 5.0, 6.0
Adding deprecations page for the upcoming Cohesivo 6.0, to let Partners know about the upcoming changes ahead of time.
For now, the following changes are covered:
As a new Rector rule is added, there's a need for dedicated Rector page:
I've extracted the exsiting content (from update_to_5.0.md and package's README) into a separate page we can refer people to.
As this might be the first time people hear about Cohesivo, I've added 2 links explaining the business reasoning.
Status: this needs to be merged with the upcoming release, as this is when the Rector rule becomes available.
Link checker results should be ignored, there's a known issue here (fixed in #3280 )
Companion PRs:
TODO BEFORE MERGING/BEFORE RELEASE
MAKE SURE da9f87a IS UP TO DATE (IMPLEMENTED AND MERGED) BEFORE THE RELEASE (https://ibexa.atlassian.net/browse/IBX-12084)