Automated publishing

Note: This article refers to the Framer desktop app. Learn more about the differences between the Framer web and desktop app here.

Because Framer Desktop projects can be set up as code repositories that use version management, they can also support multiple individuals making changes to the project at the same time.

When an individual’s changes get merged, an automated CI process can be kicked off to automatically publish a new version of the Framer package using the Framer Command Line Interface (CLI).

This integration allows teams of developers and designers (or even a single individual) to work on the same Framer project, with the knowledge that the version of the package will always be up to date.

CI

As an example of an automated publishing workflow, here is a small Circle CI configuration that uses the Framer CLI to publish a package.

Note that this example assumes that the FRAMER_TOKEN environmental variable has already been set in the CI project settings.

# Javascript Node CircleCI 2.0 configuration file
#
# Check https://circleci.com/docs/2.0/language-javascript/ for more details
#
version: 2
jobs:
publish:
docker:
- image: circleci/node:10
working_directory: ~/repo
steps:
- checkout
- run: yarn
- run: npx framer-cli publish --yes
workflows:
version: 2
publish:
jobs:
- publish:
filters:
branches:
only: master
COPY

GitHub Actions

It’s also possible to use GitHub Actions to automate the release of a Framer package without the use of a separate CI. The Framer Bridge action can be added directly from the Marketplace, and an example of a build and publish workflow, ready to be cloned, can be found here.