Remind user that cre_settings changes might involve re-proposing job-specs

[yashnevatia]

Requires

Supports

[github-actions]

👋 yashnevatia, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[github-actions]

CRE settings touched

This PR changes files under pkg/settings/.

If the settings schema changed (new/renamed/removed fields or different defaults), before merge:

1. Check chainlink-deployments for existing overrides on the affected fields (e.g. domains/cre/*/settings/*.toml).
2. Whenever this change goes live,

• Update any deployment TOMLs that still reference changed fields.
• Plan to re-propose jobs with the updated settings TOMLs.

Test-only changes under pkg/settings/ can ignore this.

[github-actions]

📊 API Diff Results

No changes detected for module github.com/smartcontractkit/chainlink-common

View full report

[Copilot]

Pull request overview

This PR adjusts CRE default settings for Aptos chain writes and adds an automated GitHub Actions reminder to flag PRs that touch CRE settings schema files.

Changes:

• Increase the default Aptos ChainWrite.ReportSizeLimit from 5kb to 6kb.
• Add a PR-commenting workflow that triggers when files under pkg/settings/cresettings/** change to remind authors to check downstream deployment overrides.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
pkg/settings/cresettings/settings.go	Updates the Aptos chain write report size default in the CRE settings schema.
.github/workflows/cre-settings-schema-reminder.yml	Adds a PR reminder workflow to highlight potential schema/default-impacting changes under pkg/settings/cresettings/**.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

CRE settings touched

This PR changes files under pkg/settings/cresettings/.
If the settings schema changed (new/renamed/removed fields or different defaults), before merge:

1. Check chainlink-deployments for existing overrides on the affected fields (e.g. domains/cre/*/settings/*.toml).
2. Whenever this change goes live,

• Update any deployment TOMLs that still reference changed fields.
• Plan to re-propose jobs with the updated settings TOMLs.

Test-only changes under pkg/settings/ can ignore this.

[github-actions]

CRE settings touched

This PR changes files under pkg/settings/cresettings/.
If the settings schema changed (new/renamed/removed fields or different defaults), before merge:

1. Check chainlink-deployments for existing overrides on the affected fields (e.g. domains/cre/*/settings/*.toml).
2. Whenever this change goes live,

• Update any deployment TOMLs that still reference changed fields.
• Plan to re-propose jobs with the updated settings TOMLs.

[github-actions]

CRE settings field deprecated

This PR adds // Deprecated in pkg/settings/cresettings/settings.go.

When making the corresponding capabilities change (where this settings field is consumed), keep the change backward compatible — the new code should still respect the old field.

Rollout:

1. Ship the capability change that reads both old and new fields.
2. After the release is live, propose job specs in chainlink-deployments using the new schema (check domains/cre/*/settings/*.toml for existing overrides on the deprecated field).
3. In a subsequent release, remove the old field from the capability code.

[github-actions]

CRE settings field deprecated

This PR adds // Deprecated in pkg/settings/cresettings/settings.go.

When making the corresponding capabilities change (where this settings field is consumed), keep the change backward compatible — the new code should still respect the old field.

Rollout:

1. Ship the capability change that reads both old and new fields.
2. After the release is live, propose job specs in chainlink-deployments using the new schema (check domains/cre/*/settings/*.toml for existing overrides on the deprecated field).
3. In a subsequent release, remove the old field from the capability code.