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 develop into master (commit to next release being breaking) #1904
Draft
alerque
wants to merge
421
commits into
master
Choose a base branch
from
develop
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alerque
added
todo
tooling
Build tooling, release management, and packaging processes
labels
Oct 30, 2023
BREAKING CHANGE: The current (pseudo) idempotent behaviour when loading a package potentially clobbers anything that has been modified since the last load. Loading a package, then modifiying a function it provides, then loading the same package again will clobber the modifiecation. This is good for idempotency but not very good for user experience when you may not be modifiying all aspects of a document render pipeline at once, as in when using templates. This change makes the default behaviour to run setting, raw handler, and command registrations only once. An altertanive to :loadpackage() called :reloadpackage() can be used to force all these registrations to be rerun when the goal is to make sure of a specific state.
Co-authored-by: Alex Orlenko <zxteam@protonmail.com>
…y building dynamic
Co-authored-by: Alex Orlenko <zxteam@protonmail.com>
…rcuit in debug builds
Includes ldoc 1.4.x → 1.5.x which we need now.
…er adds paths from env
This is cool but not very useful because it is constantly out of sync with how upstream mantains the file. Style changes, dependency changes, Ruby function changes, etc. all affect this no to mention our own local build changes. These are harder to backport to the perl than it is just to manually update the upstream formula.
These macros are identical across a bunch of projects I work on, hence the naming scheme. I eventually decided it was confusing to know which macros came from the autoconf-archive and which were my own, so not using the AX_ prefix except for things that could be dropped and used directly from the archive just makes sense.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is so I can start keeping an eye on CI status for the branch linked from the milestone...