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

Release 3.4.2 preparation #630

Merged
merged 9 commits into from
Jan 26, 2023
Merged

Release 3.4.2 preparation #630

merged 9 commits into from
Jan 26, 2023

Conversation

dbast
Copy link
Member

@dbast dbast commented Jan 25, 2023

Description

closes #629

Be carefully reviewing this, it contains more than just changelog updates: During preparing the release I looked through our Github CI runs once again, inspected all the CI logs, downloaded the created installers and inspected them. I found one logging error + a documentation error. Both are fixed by this PR including Changelog update! See the last commits in this PR. I can split this out into a separate PR, but that is no fun, given the current clogged GitHub Action runners.

Checklist - did you ...

  • Add a file to the news directory (using the template) for the next release's release notes?
  • Add / update necessary tests?
  • Add / update outdated documentation?

@dbast dbast requested a review from a team as a code owner January 25, 2023 18:33
@conda-bot conda-bot added the cla-signed [bot] added once the contributor has signed the CLA label Jan 25, 2023
@@ -94,7 +94,7 @@ def modify_xml(xml_path, info):
background_path = join(OSX_DIR, 'MacInstaller.png')

if background_path:
logger.info("Using background image", background_path)
logger.info("Using background image: %s", background_path)
Copy link
Contributor

Choose a reason for hiding this comment

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

Good catch.

Copy link
Contributor

Choose a reason for hiding this comment

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

Is this not caught by any linter? I'm surprised 🤔

Copy link
Member Author

Choose a reason for hiding this comment

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

yeah, me too. Seems like I previously only inspected the linux/windows logs and flake8 seems to not catch it (I am more used to pylint, which seems too be able to catch it... pylint is generally stricter, but also supports different code styles and options so that is hard to find an agreement what to set... flake8 is like the baseline linter, not so strict, default options are sane, extendable via extension)

After I found this one occurence, I inspected the full logs via printing stdout/stderr also in succeeding tests in my fork of the repo (where the CI was not clogged). Those logs are awesome now: you see how constructor runs start in main, continue in e.g. osxpkg, utils, fcp, back to osxpkg until it finishes etc ...

docs/source/howto.md Outdated Show resolved Hide resolved
Copy link
Contributor

@jaimergp jaimergp 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 good to go! Thanks Daniel!

@dbast dbast merged commit 29ed8bc into conda:main Jan 26, 2023
@dbast dbast deleted the release branch January 26, 2023 12:04
@github-actions github-actions bot added the locked [bot] locked due to inactivity label Jan 27, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla-signed [bot] added once the contributor has signed the CLA locked [bot] locked due to inactivity
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Release 3.4.2
3 participants