uzitech / action-setup-atom Goto Github PK

To prevent a warning message being printed on every run of Atom on Linux you'll need the RANDR extension added to the Xvfb with +extension RANDR added to the arguments (like this).

The action-setup-atom has been working fine for months. Last night it failed twice with the following message:

Run UziTech/action-setup-atom@v2
with:
version: stable
version: stable
folder: /home/runner/work/_temp/atom
/usr/bin/dpkg-deb -x /home/runner/work/_temp/59c71ac2-00f1-4b17-8931-eb1a483b2594 /home/runner/work/_temp/atom
dpkg-deb: error: '/home/runner/work/_temp/59c71ac2-00f1-4b17-8931-eb1a483b2594' is not a Debian format archive
Error: The process '/usr/bin/dpkg-deb' failed with exit code 2

You can check the actions at https://github.com/jstritch/git-tabular-diff

As an aside, the branch protection rules I have setup did not prevent Renovate from auto-merging to master when this occurred.

How do I resolve the problem(s)?

Not necessarily an issue with this Action template, but the URL here:

https://github.com/UziTech/action-setup-atom/blob/v2/src/setup-atom.js#L60

Returns 404s for Stable and Beta.

This is causing builds to fail: https://github.com/richrace/highlight-selected/pull/240/checks?check_run_id=2912963614

https://atom.io/download/deb?channel=stable => https://atom-installer.github.com/v1.57.0/atom-amd64.deb?s=1620674304&ext=.deb => 404 Blob Not Found

When trying to download the lastest stable version on https://atom.io/ it redirects to https://github.com/atom/atom/releases/tag/v1.60.0

Currently, there is no log or record of the installed Atom. I think the action should run apm --version to show the version of the Atom that is installed. This is important for future references to that job.

Hey, I tried to publish a package using this action. Unfortunately, the operation fails because it does not recognize the previous (successful) login.
https://github.com/morphy2k/linter-revive/runs/2749098886?check_suite_focus=true#step:9:9

Any idea what could be the reason for this?

Can you provide an option to setup Atom using snapcraft?

https://snapcraft.io/atom

Would it be possible to add support for selecting an exact Atom version to use, in addition to the release channels?

This way, if one wants to support e.g. Atom versions from 1.x.y onwards, they could test on the current stable and perhaps beta channels to assert latest versions support, and additionally on the minimum supported 1.x.y version to check that it's backwards compatible (all the API used is present in that older version, etc.).

At least given the same major version, this should give solid reassurance that things will work. If the stable/beta channels get hit with a new major version, that could cause problems, but I don't think there is a way to get around that currently (a way of using the latest minor version of a target major version).

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

https://github.com/thumperward/auto-create-files/runs/305993144

The specified workflow isn't doing anything clever, yet all of the configured jobs are failing, either when showing versions or when installing dependencies (of which there is only one for this package).