Skip to content

Commit

Permalink
v0.2.1 changelog
Browse files Browse the repository at this point in the history
  • Loading branch information
@BenediktBurger
BenediktBurger committed Feb 13, 2024
1 parent f0b2572 commit dc9c2c6
Showing 1 changed file with 11 additions and 1 deletion.
12 changes: 11 additions & 1 deletion CHANGELOG.md
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,14 @@
# CHANGELOG

## [0.2.1] - 2024-02-13

### Fixed

- Fix BaseCommunciator to hand over message, if it is an error message (#55)

**Full Changelog**: https://github.com/pymeasure/pyleco/compare/v0.2.0...v.0.2.1


## [0.2.0] - 2024-02-13

_Several deprecated parts are removed and inner workings are changed._
Expand Down Expand Up @@ -64,7 +73,8 @@ _Initial alpha version, complies with [LECO protocol alpha-0.0.1](https://github
@BenediktBurger, @bilderbuchi, @bklebel


[unreleased]: https://github.com/pymeasure/pyleco/compare/v0.2.0...HEAD
[unreleased]: https://github.com/pymeasure/pyleco/compare/v0.2.1...HEAD
[0.2.1]: https://github.com/pymeasure/pyleco/releases/tag/v0.2.1
[0.2.0]: https://github.com/pymeasure/pyleco/releases/tag/v0.2.0
[0.1.0]: https://github.com/pymeasure/pyleco/releases/tag/v0.1.0
[alpha-0.0.1]: https://github.com/pymeasure/pyleco/releases/tag/alpha-0.0.1

3 comments on commit dc9c2c6

@bilderbuchi
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BenediktBurger probably you've already noticed that there are warnings in the deploy build:

Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to token username with no supplied password field
deploy

Not sure if this is actionable for us (it's just a "notice" in the publish log)

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

I'm not sure where this is coming from, as we are already using v4 of setup-python?

@BenediktBurger
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there are warnings in the deploy build:

That is in the publishing action.

I'm not sure where this is coming from, as we are already using v4 of setup-python

for checkout, version 4 is the most recent, for setup-python, version 5 is the most recent. I pushed the change, also I adjusted the PR for pymeasure.

@bilderbuchi
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh, I read the message wrong: "Please update the following action: ... v4", I read as "please update to..." , and was confused. All clear now.

Please sign in to comment.