build(deps): bump org.xmlunit:xmlunit-core from 2.9.1 to 2.10.0 in /dspace-api #519
Conversation
This file contains hidden or 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
rest.cors.allowed-origins allows us to develop on Angular locally while using a remote DSpace API. We will perhaps disable this in the long run after we deploy DSpace 7.
I ported these from DSpace 6 but they are aesthetically annoying in DSpace 7 when you have more than ~4.
These were copied directly from our DSpace 6 branch.
These are the latest spider agent lists from our DSpace 6.x branch.
Sync settings with DSpace 6. We do not want to log bot requests, and we want to match user agents case insensitively.
Use a "2x" supersample by overriding the ImageMagick density from 72 to 144. This creates higher-quality PDF thumbnails.
We only want to send subscription mails for new items, not modified ones.
These behave differently in DSpace 7 than in DSpace 6 when the IDs are missing (you get infinitely repeating values in the submission form dropdown).
Our subjects are in dcterms.subject and we don't use hierarchical subjects. Also, change the date issued field.
Use dcterms.type for Type and add a few more filters from CGSpace.
Update from latest COUNTER-Robots list, removing from the local ILRI overrides where needed.
It has been ten years since we last increased the thumbnail size on CGSpace. 300px has served us well, but higher-density displays and new uses for thumbnails call for larger sizes. For reference, I checked 300 - 600px to see the implications on file size for one portrait layout PDF: - 212x300px: 31 kilobytes <--- current - 283x400px: 52 kilobytes - 354x500px: 76 kilobytes - 424x600px: 106 kilobytes I think 500px is a good compromise.
We don't use Datacite yet, but this is easy to change now so it can possibly work in the future.
We are not using this yet, but it will surely come in handy.
Copied directly from CGSpace's DSpace 6 repository.
Hopefully easier to maintain during future rebases now.
Just to show that it's possible and get feedback from our submitters.
Update a few Discovery configs to use dcterms.issued instead of dc.date.issued.
I was surprised to see this was disabled, as I already tested it a few months ago.
The DC=ILRI no longer exists in Active Directory as far as I can see from checking a few users.
There seems to be a bug in DSpace 7.6-SNAPSHOT that causes LDAP lo- gins to fail when the groupmap is enabled.
We are using an external controlled vocabulary instead. This hasn't been needed since we got rid of Atmire's Listings and Reports module in DSpace 6.
Use a list comprehension to filter out rows that are missing a url or filename.
IWMI sent me some new ones so I updated our list. This time I used
GNU `sort` instead of `sort i` in vim because GNU sort handles ac-
cents better.
Formatted with tidy:
$ tidy -xml -utf8 -m -iq -w 0 dspace/config/controlled-vocabularies/cg-creator-identifier.xml
As of DSpace 7.6.1 the community and collection subscription emails say "changed" items, which is confusing for users. Overriding this for now.
Sorted first with GNU `sort` instead of `sort i` in vim because GNU
sort handles accents better.
Formatted with tidy:
$ tidy -xml -utf8 -m -iq -w 0 dspace/config/controlled-vocabularies/cg-creator-identifier.xml
We don't need the NOOP and Register DOI curation tasks.
Enable the normalizedois and countrycodetagger curation tasks to run on workflow items. The normalizedois task runs on `editstep`, which is immediately after an item is deposited into the workflow, and for every edit step after (so up to three times depending on how the collection is configurated). The countrycodetagger task runs on `finaleditstep`, which is the last edit step (aka "Final editors" or step 3) because we don't want editors to potentially remove the country code tags. The docs allude to an "archive" step that runs just before an item is inst- alled to the archive, but it doesn't seem to work.
Bumps [org.xmlunit:xmlunit-core](https://github.com/xmlunit/xmlunit) from 2.9.1 to 2.10.0. - [Release notes](https://github.com/xmlunit/xmlunit/releases) - [Changelog](https://github.com/xmlunit/xmlunit/blob/main/RELEASE_NOTES.md) - [Commits](xmlunit/xmlunit@v2.9.1...v2.10.0) --- updated-dependencies: - dependency-name: org.xmlunit:xmlunit-core dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
alanorth
force-pushed
the
7_x-prod
branch
2 times, most recently
from
221a5f5 to
956010f
Compare
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.
Bumps org.xmlunit:xmlunit-core from 2.9.1 to 2.10.0.
Release notes
Sourced from org.xmlunit:xmlunit-core's releases.
Changelog
Sourced from org.xmlunit:xmlunit-core's changelog.
Commits
33a5d6afix release numbereceec4ajavadocs75828fdCreate SECURITY.mddcaafe9record extension function changes611f6betry to disable extension functions for XPathsb81d48bdisable XSLT extension functions by default, add more configurersba14909XMLUnit 1.x is no longer maintainedcd6731ethis is going to be a feature release, not a bugfix releasec47d390record last changes5141915add byNameAndAllAttributes that uses an attrbute filterDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.