Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge 6.0.0 changes into main #3133

Merged
merged 225 commits into from
Jan 8, 2025
Merged

Merge 6.0.0 changes into main #3133

merged 225 commits into from
Jan 8, 2025

Conversation

krzywon
Copy link
Contributor

@krzywon krzywon commented Oct 24, 2024

Description

This is the last merge of the release_6.0.0 branch to go into main. All of the changes were previously approved, but there were merge conflicts in two files, ci.yml and DocViewWidget.py/

Review Checklist:

Documentation (check at least one)

  • There is nothing that needs documenting
  • Documentation changes are in this PR
  • There is an issue open for the documentation (link?)

Installers

  • There is a chance this will affect the installers, if so
    • Windows installer (GH artifact) has been tested (installed and worked)
    • MacOSX installer (GH artifact) has been tested (installed and worked)

Licencing (untick if necessary)

  • The introduced changes comply with SasView license (BSD 3-Clause)

wpotrzebowski and others added 30 commits June 28, 2024 15:02
…installers need to install some packages before others
…new plots from getting the transforms of previous plots
…sure teh uninstall name is unique from version to version
…e formula includes the density and is incomplete
Check successful launch of sasview on CI (linux)
klytje and others added 21 commits October 22, 2024 18:38
…ndow, but remove mention of documentation generation
Release 6.0.0: Show 404 message instead of regen
@wpotrzebowski
Copy link
Contributor

Shouldn't we deal with the three remaining 6.0.0 PRs before merging to main? I am particularly thinking of #2181

@lucas-wilkins
Copy link
Contributor

Shouldn't we deal with the three remaining 6.0.0 PRs before merging to main? I am particularly thinking of #2181

I think we need to get it merged!

Copy link
Contributor

@lucas-wilkins lucas-wilkins left a comment

Choose a reason for hiding this comment

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

This is pretty hard to follow in detail, but as far as the merge conflict goes, @krzywon is the one who will know best. I say merge.

@lucas-wilkins lucas-wilkins merged commit a8902fd into main Jan 8, 2025
19 checks passed
@lucas-wilkins lucas-wilkins deleted the merge-6-0-0-into-main branch January 8, 2025 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.