Issue description

Please tell me the detailed specifications of the automatic updates described in Update Serverless Framework and how to pin a version described in Serverless Framework version pinning.

Questions

1. Please tell me all the timing and conditions under which automatic updates run.
   • I think that automatic updates occur when you run a serverless update and every 24 hours (when you run any serverless commands after the updateLastChecked time recorded in ~/.serverless/binaries/metadata.json has passed), is that correct? And, are there any other times when automatic updates occur?
2. What specifically happens if SERVERLESS_FRAMEWORK_FORCE_UPDATE=true is set?
3. What specifically happens if SERVERLESS_FRAMEWORK_FORCE_UPDATE=false is set?
4. Does the Serverless Framework's automatic update mechanism ignore the version specification in Node.js npm's package.json?
5. Is there a way to stop automatic updates?
   • I tried setting SERVERLESS_FRAMEWORK_FORCE_UPDATE=false in the environment variable, but the automatic update did not stop. If you want to fix the version used by serverless deploy, is it only possible to specify frameworkVersion in serverless.yml in the way written in Serverless Framework version pinning with frameworkVersion in serverless.yml?
6. When pinning the Serverless Framework version with frameworkVersion in serverless.yml, is there any way to reference the value in an external file? (I'd like to write the version in one configuration file and reference it from serverless.yml for multiple CloudFormation stacks.)
7. What are the meanings of the following (1)~(3) parameters in meta.json created when deploying CloudFormation stacks with Serverless Framework?
   • When deployed with the frameworkVersion: '4.4.4' in serverless.yml referring to an external file, the Serverless Framework version value output to .serverless/meta.json appears to be different.

• serverless.yml

︙
    frameworkVersion: ${file(. /config.yml):frameworkVersion}
︙

• config.yml

︙
    frameworkVersion: '4.4.4'
︙

• .serverless/meta.json

    {
        "/path/to/serverless": {
        "versionSfCore": null,
        "versionFramework": "4.4.6", ... (1)
        ︙
        "composeResolverProviders": {
        "file": {
            "instance": {
            ︙
            "serviceConfigFile": {
                ︙
                "frameworkVersion": "4.4.4", ... (2)
        ︙
        "versionSf": "4.4.6", ... (3)

Context

• Serverless Framework: 4.4.6 (the value of frameworkVersion in serverless.yml is '4.4.4')