prinzpiuz / msm Goto Github PK

🚨 The automated release from the new_Design branch failed. 🚨

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

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 fix 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 new_Design branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are 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.

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

Good luck with your project ✨

Your semantic-release bot 📦🚀

deletion is happening successfully, But deleted files are not clearing from the listing

Implement wake on lan using this library

Seems you (accidentally) used the wrong key to sign your latest release (v1.6.0):

Signer #1 certificate DN: C=US, O=Android, CN=Android Debug
Signer #1 certificate SHA-256 digest: b7f8f930495108b98fccf0c2eedb288182a49f2b5a9055e62292abb35299edb8
Signer #1 certificate SHA-1 digest: b9d1fb1650c513e784f62a37aa9db73cc6fa29dd
Signer #1 certificate MD5 digest: 9a0ae4c7cbc14cd1afdaba90a8b74dd7
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048

That's a debug key.Checking the last version I had here before (v1.0.0), it's a debug key as well – just a different one:

Signer #1 certificate DN: C=US, O=Android, CN=Android Debug
Signer #1 certificate SHA-256 digest: ef4a7b8f4a0235e079f2aa9246cb58727f7e1eb240e6ffa5e3e459fd157d8bdd
Signer #1 certificate SHA-1 digest: add3d15f65a07fb11b402283bbb2bccaeeac1df5
Signer #1 certificate MD5 digest: e373b2c6cf41ff6e46ec553dea5dd25d
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048

Is that related to #28 – and do you by any chance generate a new debug key with every release? That would be bad as it makes updates impossible (key mismatch; Android will refuse updates then). Any chance this will be fixed in the near future – and you'll be using a proper release key?

currently changelog generated in the workflow is not correct