Always include the dependency reference in the push publishing manifest file

[swicken-dotcms]

Parent Issue

No response

Problem Statement

When the manifest is generated, we add a column that shows what name/identifier caused that object to be considered a dependency of the bundle.

We do not populate that column if the object is excluded from the bundle by mod_date.

This makes it challenging to troubleshoot dependency chains, as other things may be included by dependency to that excluded object, and we do not know what the excluded object was a dependency of.

Steps to Reproduce

1. Set up a push publishing environment with the demo starter
2. Push the entire site, check the manifest, and you will see all of the dependency references added
3. Save/publish one piece of content
4. Push the entire site; only the modified content will have its dependency reference

Acceptance Criteria

Always include the dependency reference, column name is included by Should look like this, with the last column populated for every row

Rename the column to 'Reason to be evaluated'.

dotCMS Version

master, all LTS versions

Proposed Objective

Customer Support

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

Related ticket: https://dotcms.zendesk.com/agent/tickets/115864

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response