@Mark Takata (Adobe) Is there a way to pin a CF version in CFPM without explicitly having to declare a version in cfpm for each package? (install PACKAGENAME[:VERSION]) I've finally got my CF2021 Docker stack up for our local development environment and while building things I discovered that CFPM will install core CF updates which is going to be problematic. For example say we're on CF2021 Update 10 in Production. In our local dev environment we build from scratch in Docker - so we download the CF2021 installer, download the Update 10 jar and install. All set. Until I need to rebuild my dev environment. Now I re-run CFPM and it will complain and automatically update to 11. And now we're out of sync with our Prod environment. You are assuming I want a core update when I may not. I this case I just want the latest package updates for the particular version of CF I'm running.

#12 5.645 ------------------------------------------
#12 5.646  Welcome to the ColdFusion Setup Wizard 
#12 5.646 ------------------------------------------
#12 5.708 ColdFusion 2021 is set up to start on boot
#12 5.732 Starting ColdFusion 2021 server ...
#12 12.74 ======================================================================
#12 12.74 ColdFusion 2021 server has been started.
#12 12.74 ColdFusion 2021 will write logs to /opt/ColdFusion/cfusion/bin/../logs/coldfusion-out.log
#12 12.74 ======================================================================
#12 42.81 Stopping ColdFusion 2021 server, please wait
#12 52.99 ColdFusion 2021 server has been stopped
#12 52.99 
#12 52.99 Applying ColdFusion updates...  
#12 83.95 ColdFusion updates applied
#12 83.95 
#12 83.95 Installing ColdFusion Packages... (this may take a moment) 
#12 83.95 
#12 90.09 The following packages will be installed : adminapi:2021.0.05.330109,administrator:2021.0.11.330247,caching:2021.0.05.330109,document:2021.0.11.330247,image:2021.0.11.330247,zip:2021.0.05.330109,spreadsheet:2021.0.11.330247,mysql:2021.0.05.330109,mail:2021.0.11.330247,feed:2021.0.05.330109,debugger:2021.0.11.330247,chart:2021.0.05.330109,ajax:2021.0.05.330109
#12 90.10 One or more packages require the server to be at update 11. Since the server is at update 10, installing the update 11 of the server.

This would be the same issue in Production if we had our builds automated. We have 3 boxes on update 10. We build a new box, it runs CFPM and installs update 11. It seems like this may have changed in Update 11? The docs mention a confirmation message - "After you run cfpm>install all, the core server gets updated for a few packages. You also view a confirmation message for the installation." But I don't see anyway to toggle that in an automated environment like Docker.

@Jim Priest Is this what you're asking for? https://tracker.adobe.com/#/view/CF-4215444

Interesting. Thankfully Adobe provide a detailed entry of said fix and... oh wait. No they didn't . So maybe I need to wait until Update 12 LOL head desk

12.5 at the LATEST

To followup - this seems to be addressed in update 11. Before: Scenario 1 - I don't do any hotfixes, just install the original CF installer, run cfpm and it updates to 11. Scenario 2 - Install via the original CF installer, install Update 10. Run cfpm and it will update to 11. With Update 11: Scenario 2 - Install via the original CF installer, install Update 11. Run cfpm and it did NOT update to 12.