Skip to content

Commit

Permalink
Version bump for release v1.3.0
Browse files Browse the repository at this point in the history
  • Loading branch information
Neverhorst committed Dec 20, 2022
1 parent 9aacb13 commit 7163e90
Show file tree
Hide file tree
Showing 3 changed files with 22 additions and 1 deletion.
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@ body:
description: What version of our software are you running?
options:
- Development
- Release v1.3.0
- Release v1.2.0
- Release v1.1.0
- Release v1.0.1
Expand Down
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.2.1.dev0
1.3.0
20 changes: 20 additions & 0 deletions docs/changelog.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,19 +5,39 @@
### Breaking Changes
None

### Bugfixes
None

### New Features
None

### Other
None


## Version 1.3.0
Released on 20.12.2022

### Breaking Changes
None

### Bugfixes
- NULL bytes in log messages are handled now and no longer lead to crashes of qudi. They are
replaced by the corresponding hex literal "\x00".
- Rubberband selection of utility plot widgets now works for `pyqtgraph != 0.12.4`. This specific
version is broken in that regard and a comprehensive error is thrown if it is detected.
- Adjusted 2D gaussian fit arguments to be compatible with the datafitting toolchain.

### New Features
- Multiple qudi sessions can now be run in parallel locally. However, the user must ensure
non-conflicting socket server settings for namespace server and remote module server in the
configs to load.

### Other
- Bumped minimum package requirement `pyqtgraph >= 0.13.0`.
- Introduced properties to make `qudi.util.constraints.ScalarConstraint` mostly backwards
compatible with the deprecated `qudi.core.interface.ScalarConstraint`. Only exception is `unit`
which should not be supported anymore.


## Version 1.2.0
Expand Down

0 comments on commit 7163e90

Please sign in to comment.