Repository navigation
Version Bump to v2.2.0 - #1174
Draft
McNamara84 wants to merge 470 commits into
Draft
McNamara84 wants to merge 470 commits into
McNamara84 wants to merge 470 commits into
Conversation
McNamara84
added
Dokumentation
This was
linked to
issues
Jul 22, 2026
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Comment on lines
+10
to
+33
| runs-on: ubuntu-latest | ||
| steps: | ||
| - name: Checkout repository with full history | ||
| uses: actions/checkout@v4 | ||
| with: | ||
| fetch-depth: 0 | ||
|
|
||
| - name: Get latest release | ||
| id: release | ||
| env: | ||
| GH_TOKEN: ${{ github.token }} | ||
| run: | | ||
| TAG=$(gh release view --json tagName --jq .tagName) | ||
| echo "tag=$TAG" >> "$GITHUB_OUTPUT" | ||
| echo "Latest release: $TAG" | ||
|
|
||
| - name: Push tag and state to GitLab | ||
| env: | ||
| GITLAB_TOKEN: ${{ secrets.GITLAB_TOKEN }} | ||
| TAG: ${{ steps.release.outputs.tag }} | ||
| run: | | ||
| git remote add gitlab "https://oauth2:${GITLAB_TOKEN}@git.gfz-potsdam.de/data_services/elmo.git" | ||
| git push gitlab "refs/tags/${TAG}:refs/tags/${TAG}" | ||
| git push --force gitlab "refs/tags/${TAG}^{commit}:refs/heads/main" |
This was referenced Aug 7, 2026
…lity Fix: elmogem platforms visibility
Chore: named volumes in Docker compose.
…e more horizontal space
Test: check that the API is fully represented in the dropdowns
Fix: hardcoded assumptions in the changelog tests
…t-address Fix: elmogem compose needs to instanciate XML submit address
Owner
Author
|
Suggestion: In the future we should squash all PR Merges into the |
…m root normally and added applyTranslationsTo to apply translations to any given domain.
Data Sources formgroup: layout improvement and documentation enrichment
* Persist resource information payload, versions and title order * Unify resource information form state and title ordering * Import resource information through DataCite XSLT * Separate DOI prefill and enforce GFZ DOI submission policy * Expand resource information help and translated DOI guidance * Complete resource information audit and changelog * Remove obsolete resource information migration * Rename resource information template for CI naming rule * Update Playwright coverage for resource information flow * Expect normalized ICGEM version on XML reimport * Keep ICGEM numeric parsing outside version assertion * Keep rejected DOIs visible and ignore stale lookup results * Correct GFZ DOI curation mail encoding * Document resource information import and payload contracts * Cover blocked external DOI and browser console in Playwright * Clarify DOI import and rejection behavior in README * Validate optional resource version in shared field validator * Keep DOI metadata search neutral and clear stale feedback * Align DOI metadata search control across screen sizes * Place submission DOI edit and help controls side by side * Clarify DOI metadata import copy in all languages * Keep DOI import action on one line on wide screens * Prevent mobile title controls from overlapping title type * Document review fixes in changelog * Show title drag handle without button border * Explain DOI metadata reuse in Resource Information guide * Accept DOI resolver links in metadata import * Use a neutral search icon for DOI metadata import * Document DOI import review improvements
* Merge contributor templates * Convert old people drafts * Restore old drafts safely * Use card stacks for imports * Reset and validate shared cards * Remove old people form groups * Use whole contributor cards * Protect draft edge cases * Clean up import test fixtures * Keep incomplete affiliations * Test shared contributor cards * Use stacks in browser fixtures * Select resource types by name * Test old draft restoration * Use contributor cards in XML tests * Fix instrument import test setup * Document draft migration * Explain draft restore safeguards * Fix ICGEM contributor contacts * Test ICGEM contact imports * Allow websites without a prefix * Test contact website validation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Draft for new version. Please do not review. Ownly for showin merge conflicts.
Planned release of v2.2.0 on 07.10.2026.
Please add your issues to be closed at this date to this PR!
Changes
[What changes have you made?]
Notes for Reviewer
[Describe the steps needed to test this]
Checklist
Branching Strategy:
If this is a hotfix: The branch was created from
mainand will be merged intomain.If this is a feature or documentation change: The branch was created from
devand will be merged intodev.If this is a feature or documentation branch, I have pulled the latest changes from
maininto my branch.Code Quality
Documentation
Testing
Known Issues
[What lower priority problems remain?]