Skip to content

Freeze versioning on Adobe Acrobat Pro (macOS) - #36609

Merged
allenhouchins merged 1 commit into
mainfrom
allenhouchins-freeze-acrobat-pro
Dec 3, 2025
Merged

Freeze versioning on Adobe Acrobat Pro (macOS)#36609
allenhouchins merged 1 commit into
mainfrom
allenhouchins-freeze-acrobat-pro

Conversation

@allenhouchins

Copy link
Copy Markdown
Member

Freezing Adobe Acrobat Pro on macOS. They recently updated the product but did not update the installer leading to validation issues on our end. I am freezing this and will check back in a few days to see if it has been updated or if we need to update our validation.

@allenhouchins
allenhouchins marked this pull request as ready for review December 3, 2025 02:20
@allenhouchins
allenhouchins merged commit c8d5812 into main Dec 3, 2025
6 of 8 checks passed
@allenhouchins
allenhouchins deleted the allenhouchins-freeze-acrobat-pro branch December 3, 2025 02:20
allenhouchins added a commit that referenced this pull request Aug 1, 2026
…1691 (#50370)

Automated unfreeze probe, revised after validation. The full unfreeze
failed: the Homebrew cask
reports 26.001.21771 (tracking Adobe's updater manifest), but Adobe's
version-less web installer
DMG still delivers 26.001.21691, so the validator's post-install osquery
check failed at
26.001.21771 — the same installer-lags-manifest behavior that caused the
original freeze.

This PR instead pins the output manifest to 26.001.21691 (the version
the DMG actually installs,
confirmed by the 2026-08-01 validator run) and keeps `"frozen": true` so
the nightly ingester
doesn't bump it back to the cask version.

Frozen since: 2025-12-02 (#36609 — "product updated but installer was
not, causing validation issues")
Version: 26.001.21662 -> 26.001.21691 (cask claims 26.001.21771;
installer not updated yet)

Note: the regenerated manifest also picks up a newer
`uninstall_script_ref`, because the frozen
output missed the script-template updates that landed on main while it
was pinned.

Draft until validation reports. Merge only if the FMA checks are green
and the validate shard
actually ran for this slug.

**Related issue:** NA

# Checklist for submitter

- [x] QA'd all new/changed functionality manually — pending CI
validation, see above.

---
_Generated by [Claude
Code](https://claude.ai/code/session_01EBxhs5D65LRUwCEJejBLJH)_

---------

Co-authored-by: allenhouchins <allen@fleetdm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants