{"version":"2.1.281","anchor":"plugin-marketplace-ref-field-accepts-branch-or-tag-sha-is-o","canonical_anchor":"plugin-marketplace-ref-field-accepts-branch-or-tag-sha-is-o","heading":"Plugin marketplace Ref field accepts branch or tag; SHA is only required for auto_install\/required","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/plugin-marketplace-ref-field-accepts-branch-or-tag-sha-is-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Plugin marketplace Ref field accepts branch or tag; SHA is only required for auto_install\/required\n\nThe plugin marketplace Ref field accepts a branch, tag or commit SHA; a full SHA is only needed for auto_install and required\n\n**What**\n\nIn the plugin marketplace settings form, the Ref field (which picks the version of the marketplace to use) now says it accepts a branch, a tag or a commit SHA. A commit SHA is the long code that identifies one exact saved version in git. The description now states that a full 40-character SHA is only needed for `auto_install` and `required`.\n\n**Why**\n\nFor most marketplaces you can enter a branch or tag name, and only need the exact SHA when a plugin is installed automatically or required.\n\n- Area: Plugins\n- Names: `auto_install`, `required`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}