During a recent upgrade, our application ruleset version rolled over from 01‑01‑99 to 01‑02‑01. After the rollover, I noticed that the changes merged into 01‑02‑01 did not take effect until I updated the Application rule to reference version 01‑02 instead of 01‑01.
Once the application ruleset version was updated, the expected changes appeared as expected.
Before promoting this change to UAT and Production, I wanted to ask:
Are there any other places besides the Application rule that might be impacted by a ruleset version rollover like this?
Are there any best practices or checks we should perform when moving this change across environments (e.g., ruleset stacks, blocked rulesets, patches, or dependencies)?
One other area to review is the Product rule used for deployments. If the Product rule references specific ruleset versions, make sure it includes the new minor version; otherwise, you may deploy an older ruleset version.
In general, when a ruleset rolls from 01-01-99 to 01-02-01, it is expected to rebase the application by updating the Application rule to reference the new minor version. At my client, where we do bi-weekly production releases, rebasing is a standard post-release activity. We update both the Application rule and Product rule to point to the new minor version.
I would also verify the Ruleset Stack to ensure all application and dependent rulesets are resolving to the expected versions. This helps prevent rule resolution and deployment issues when promoting to higher environments.