Add ta-blnet 1.0.36 to stable

[weberk]

Please update my adapter ioBroker.ta-blnet to version 1.0.36.

This pull request was created by https://www.iobroker.dev c0726ff.

• Addition to Latest was done via PR Add ta-blnet to latest #4334
• Testing was covered by discussion at https://forum.iobroker.net/topic/78225/test-adapter-ta-blnet-npm-latest

[weberk]

Yes, I want to release 1.0.36 which has only some translations different to 1.0.35.

1.0.34 was released only to GitHub, but was failing lint check. I would like to keep the changes in version history.
(see:
[E254] Version "1.0.34" listed at common.news at [io-package.json](https://github.com/weberk/ioBroker.ta-blnet/blob/master/io-package.json) does not exist at [NPM](https://www.npmjs.com/package/iobroker.ta-blnet). Please remove from news section.)

[mcm1957]

The problem with such fake news is that admin lists those release when selection install dedicated release but this of course fails as the release is not available at npm.

So if possible move the info to the next release. Otherwise we must live with potenzial user issues that release x.y.z.cannot be installed. I do not consider this blocking.

[weberk]

I merged version comment of 1.0.34 to version comments of 1.0.35. They will disappear in some next stable release.

[github-actions]

Automated adapter checker

ioBroker.ta-blnet

-

👍 No errors found

Adapter releases: https://www.iobroker.dev/adapter/ta-blnet/releases
Adapter statistic: https://www.iobroker.dev/adapter/ta-blnet/statistics

History and usage information for release 1.0.36:

1.0.36 created 4.1.2025 (2 days old)
3 users (16.67%)

stable release not yet available

Please verify that this PR really tries to update to release 1.0.36!

Add comment "RE-CHECK!" to start check anew

[github-actions]

ioBroker repository information about STABLE-BRAND-NEW tagging

Your PR has been tagged with the label STABLE - BRAND NEW. This indicates that the release requested to be added to the stable repository seems to be too young for immediate processing.

Normally, a release should be available at LATEST repository for at least one or two weeks without any serious issues detected within this timeframe. Your release seems to be younger than 7 days.Your PR will be kept in evidence and will be merged approximately one week after creation of the release without any further action required by you.

IMPORTANT:
Of course, it is possible to release a new version immediately if it is a hotfix for a serious problem, i.e. some errors cause adapter crashes or incompatible api changes of external websites blocking normal usage. In this case, please indicate this fact as a comment and mention mcm1957 and eventually Apollon77 explicitly. Please describe the reason (i.e. by referencing an issue). Hotfixes should minimize the changes, even dependency updates should be avoided if not related to the fix. New functionality and major (breaking) updates are most likely never a hotfix.

Please note that ANY (even hotfixes) should be available at latest repository for at least 1 day and have some (few) installations to avoid hotfixes with serious problems at stable repository. Exceptions to this minimal delay must be discussed individually.

Feel free to contact me (mcm1957) if you have any more questions.