add standard test-and-release workflow #2844
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR provides the standard test-and-release workflow.
Tests are condfigured to run on all supported platforms and on node.js 20 and 22 - matching engines clause at package.json.
integrrated deploymet to npm is disabled. Feel free to enable it if you want to use. But its fully ok to continue using your working environment.
linter checks ere disabled as eslingt is not installed currently. If you wangt to use lint in future, please let me know - theres a new package @iobroker/eslint-config which provides a common set of rules and includes all required nom packages. A migration / installation guide is currently at review and will be published within the next two weeks - if everythiung is ok.
Again - using lint is completly optional although recommended. As linter / prettier most likely will require some changes to code you should be orepared to review / solve them if you want to use lint. But this is completly your decision,
This PR provides all tests which are required for all adapters (unless discussed for special cases). The tests pass at my fork so they should pass at your repo too. Theres NO change to any code required or delivered.
Please review / merge / test if its ok for you.
THANKS for spending time to maintain an ioBroker adapter.
Fell free to ask if you have any questions.