Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automated releases #2708

Open
Tracked by #2677
six7 opened this issue Apr 30, 2024 · 1 comment · May be fixed by #3093
Open
Tracked by #2677

Automated releases #2708

six7 opened this issue Apr 30, 2024 · 1 comment · May be fixed by #3093

Comments

@six7
Copy link
Collaborator

six7 commented Apr 30, 2024

One annoyance we have with working with the Figma plugin right now is the way we have to do releases. It's all very manual, requiring us to download or build the plugin, and then go to Figma, hit Manage plugins in development and go to Publish a new release for our plugin + enter something in the changelog. This means that even for small hotfixes we have to do all of this manual effort.

Solution

We'd love some automated way of doing this. Whenever we merge to main or when we trigger a certain action using GitHub Actiosn, we'd like the plugin to be released based on the version specified (e.g. when from main build from that and trigger a release). This would mean we get into a habit of releasing often, we'd merge in a hotfix and a new release is deployed.

Possible tools

There's https://github.com/parrot-global/figcd which is supposed to do this, but we've not been able to get that to run successfully.

Definition of done

  • We have successfully tested a spike with a dummy plugin (or one of our other ones, ask @six7)
  • We have a GitHub Actions script that releases plugins to a certain output
  • As a last resort, we could always fall back to a Macbook that sits in the Himalayas and is triggered to release 🤓
@six7 six7 mentioned this issue Apr 30, 2024
@six7 six7 moved this from 📥 Triage to 📤 Ready for dev in Tokens Studio for Figma Roadmap Apr 30, 2024
@six7 six7 moved this from 📤 Ready for dev to ⚙️ Shaping Engineering in Tokens Studio for Figma Roadmap Jul 8, 2024
@macintoshhelper
Copy link
Contributor

Pros

  • Save time for doing releases, less manual work
  • We can get into a habit of releasing often, can merge in a hotfix and a new release is deployed.

Cons

  • Could break from time to time, as unstable APIs are being depended upon

Blocked By/Depends On

  • Need to fork/contribute upstream a fix for authentication to use figcd

Suggested Actions

  • Spike with figcd
  • Choose the best option:
    • figma-linux + Playwright integration
    • figcd

Amount of Time to Implement: Small/medium – 1-3 days, depending on whether there are blocking issues due to breaking API changes

Resources

@macintoshhelper macintoshhelper moved this from ⚙️ Shaping Engineering to 🕜 In Progress in Tokens Studio for Figma Roadmap Jul 19, 2024
@macintoshhelper macintoshhelper self-assigned this Jul 19, 2024
@six7 six7 added this to the Improved Developer Experience milestone Jul 22, 2024
@macintoshhelper macintoshhelper linked a pull request Aug 21, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🕜 In Progress
Development

Successfully merging a pull request may close this issue.

3 participants