Releases: MethodicalAcceleratorDesign/MAD-NG.py
Releases · MethodicalAcceleratorDesign/MAD-NG.py
Release v0.9.1
What's Changed
- Bump myst-parser from 4.0.1 to 5.0.0 by @dependabot[bot] in #42
- Bump sphinx-rtd-theme from 3.0.2 to 3.1.0 by @dependabot[bot] in #41
- Bump MAD-NG to 1.1.12 and pymadng to 0.9.1 by @jgray-19 in #43
New Contributors
- @dependabot[bot] made their first contribution in #42
Full Changelog: v0.9.0...v0.9.1
Release v0.9.0
Changelog
- Remove support for Python 3.10, now only supporting Python 3.11 and above.
- Replaced incorrect Warning call with logging.warning for proper warning handling.
- Also add the .close() method to the MAD class, allowing users to explicitly close the MAD-NG process and clean up resources.
What's Changed
Full Changelog: v0.8.4...v0.9.0
v0.8.4
v0.8.3
v0.8.2 Release
The only significant change is moving from MAD-NG 1.1.6 to 1.1.8
What's Changed
- Add GitHub Action workflow for bumping MAD-NG release by @Copilot in #30
- Add package version bump to MAD-NG release workflow by @Copilot in #32
- Bump MAD-NG to 1.1.7 and pymadng to 0.8.2 by @jgray-19 in #33
- Bump MAD-NG to 1.1.8 and pymadng to 0.8.2 by @jgray-19 in #34
New Contributors
- @Copilot made their first contribution in #30
Full Changelog: v0.8.1...v0.8.2
v0.8.1
v0.8.0
What's Changed
- Add ruff rules to repository by @jgray-19 in #28
- Added comprehensive ruff configuration in pyproject.toml with various linting rules
- Renamed classes and functions to follow PascalCase and snake_case conventions
- Updated imports to use pathlib.Path instead of os.path
- Improved code formatting and removed redundant constructs
- BUG: Fixed used of py instead of py_name, resulting in py_name being unuable.
- Removed compatibility for Python versions below 3.10, now only supporting Python 3.10 and above.
- Updated documentation to reflect changes in code style and conventions.
Full Changelog: v0.7.1...v0.8.0
v0.7.1
v0.7.0
What's Changed
The transfer of dicts now means that lists previously transferred using pymadng will now be broken. You will need to use the py:send(tbl, true) to send a shallow copy. Or if using the higher level, you must use .eval()
Full Changelog: v0.6.3...v0.7.0