Spin up a Patch Development Org from your Partner Business Org, apply the fix, upload the patch, and ship it to subscribers via Push Upgrade.
- Click New Patch
From the package detail page in your Partner Business Org, click New Patch. Select the base major version you are patching. Salesforce provisions a Patch Development Org seeded with that version.
- Log into the PDO and apply the fix
The PDO has the package metadata pre-installed. Make only the changes the patch namespace permits. The platform blocks disallowed changes at save time.
- Run apex unit tests
Every patch must keep code coverage above 75 percent. Run Apex Tests in the PDO. Fix any test failures before upload, because security review will not run but the upload check still runs the tests.
- Optionally upload a Beta
For risky fixes, upload as Beta first. Install the beta into two or three friendly subscribers. Validate. The beta expires in 30 to 60 days; promote to a real patch when you are satisfied.
- Upload the final patch
Back in the Partner Business Org, click Upload on the patch version. Salesforce produces a new install URL and increments the patch number (1.4.2 to 1.4.3).
- Push to subscribers
Open the Subscriber Support Console. Schedule a Push Upgrade to a wave of subscribers (start small, expand). Monitor the console for failures.
Provisioned org locked to the patch namespace where the fix is built and tested.
Time-limited patch upload for friendly testing. Cannot be pushed; expires in 30 to 60 days.
The third position in the version number (1.4.X). Increments on each upload.
Delivery channel that lands the patch in every selected subscriber org automatically.
- The patch namespace blocks any change that would break compiled Apex or invalidate subscriber data. If your fix requires a field removal or a method signature change, plan for the next major version.
- Patch Releases skip security review but still require 75 percent code coverage at upload. Add tests for the fix before clicking Upload.
- Beta patches expire on their own. Do not build long-term subscriber relationships against a beta version; promote to a real patch before the expiration.
- Patches accumulate. A subscriber on 1.4.1 jumping to 1.4.7 gets every intermediate change rolled in. Test the cumulative effect, not just the single fix you wrote.