Conversation
Bumps [tmp](https://github.com/raszi/node-tmp) from 0.2.1 to 0.2.5. - [Changelog](https://github.com/raszi/node-tmp/blob/master/CHANGELOG.md) - [Commits](raszi/node-tmp@v0.2.1...v0.2.5) --- updated-dependencies: - dependency-name: tmp dependency-version: 0.2.5 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
…/evoks/theme/static_src/tmp-0.2.5 Bump tmp from 0.2.1 to 0.2.5 in /evoks/theme/static_src
Bumps [eazy-logger](https://github.com/shakyshane/easy-logger) from 4.0.1 to 4.1.0. - [Commits](shakyShane/eazy-logger@v4.0.1...v4.1.0) --- updated-dependencies: - dependency-name: eazy-logger dependency-version: 4.1.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Improve email support and skosmos behaviour
…/evoks/theme/static_src/eazy-logger-4.1.0 Bump eazy-logger from 4.0.1 to 4.1.0 in /evoks/theme/static_src
WalkthroughUpdated Skosmos build context references in docker-compose.yml from v2.17 to v3.0 for both skosmos-dev and skosmos-live services, pointing to NatLibFi/Skosmos.git#v3.0. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## development #294 +/- ##
============================================
Coverage 92.31% 92.31%
============================================
Files 50 50
Lines 1848 1848
============================================
Hits 1706 1706
Misses 142 142 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docker-compose.yml`:
- Around line 164-165: The Skosmos v3.0 docker image in docker-compose.yml is
fine but v3.0 introduces breaking changes in config.ttl; update
./skosmos-dev/config.ttl and ./skosmos-live/config.ttl to rename properties
skosmos:uiHoneypotEnabled→skosmos:feedbackHoneypotEnabled and
skosmos:uiHoneypotTime→skosmos:feedbackHoneypotTime, remove obsolete plugin
props (skosmos:hasParamPlugin, skosmos:hasPlugin, skosmos:useParamPlugin,
skosmos:usePlugin) and replace them with skosmos:globalPlugins and
skosmos:vocabularyPlugins, and migrate any Twig snippet-based UI customizations
(about.inc, footer.inc, etc.) into custom-templates/*.twig; ensure both config
files are validated before deployment.
| context: https://github.com/NatLibFi/Skosmos.git#v3.0 | ||
| dockerfile: dockerfiles/Dockerfile.ubuntu |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check if v3.0 tag exists in Skosmos repository
echo "=== Checking Skosmos repository tags ==="
git ls-remote --tags https://github.com/NatLibFi/Skosmos.git 2>/dev/null | grep -E 'v3\.' | head -20Repository: kit-data-manager/EVOKS
Length of output: 671
🌐 Web query:
Skosmos v3.0 release breaking changes migration
💡 Result:
Skosmos v3.0 (released Dec 10, 2025) — breaking changes & migration checklist
1) Runtime/build prerequisites
- PHP: Skosmos 3 requires PHP 8.1+ (8.1–8.4 supported). [1]
- Front-end build: the UI was reimplemented with Bootstrap 5 + Vue.js 3 (Cypress tests added). If you deploy from source (not Docker), expect updated front-end tooling compared to Skosmos 2. [2]
2) Configuration (config.ttl) breaking changes
Skosmos 3 is still configured via config.ttl (copy from config.ttl.dist). [3]
Renamed properties (update your config.ttl):
skosmos:uiHoneypotEnabled→skosmos:feedbackHoneypotEnabled[4]skosmos:uiHoneypotTime→skosmos:feedbackHoneypotTime[4]
(These new names are also reflected in the Skosmos 3 configuration docs.) [3]
3) Plugin configuration breaking changes
Skosmos 3 simplifies plugin enablement:
- Global plugins: use only
skosmos:globalPluginson the globalskosmos:Configuration. [5] - Vocabulary plugins: use only
skosmos:vocabularyPluginson eachskosmos:Vocabulary. [5]
Removed/obsolete plugin mechanisms from Skosmos 2 (must be removed from configs):
- Vocabulary-level
skosmos:hasParamPluginandskosmos:hasPluginare removed in Skosmos 3. [5] - Legacy activation/config options
skosmos:useParamPluginand standaloneskosmos:usePluginare dropped; configuration is now only viaskosmos:globalPluginsandskosmos:vocabularyPlugins. [4]
4) Translations workflow changed
- Skosmos 3 switched its translation framework to Lokalise (process differs from Skosmos 2). [1]
If you share your current config.ttl (especially plugin bits), I can point out the exact lines to change for a clean Skosmos 2 → 3.0 migration.
🌐 Web query:
Skosmos v3.0 configuration file format changes
💡 Result:
Skosmos v3.0 keeps configuration in a single Turtle (RDF) file named config.ttl, organized as: (1) global configuration + (2) vocabulary-specific configuration (vocabularies are declared as RDF resources in the same file). Global settings are given as properties on an instance of skosmos:Configuration, and each vocabulary is a skosmos:Vocabulary instance (a void:Dataset). [1]
What did change in the “configuration format / layout” going into Skosmos 3 is mainly the cleanup/overhaul of legacy configuration and customization mechanisms (called out as “Skosmos 3 configuration overhaul” in the 3.0-beta.1 release notes). [2] In particular:
- UI customization moved away from Skosmos 2’s
view/*.incTwig-snippets (e.g.,about.inc,footer.inc,left.inc,right.inc) [3] to Skosmos 3’scustom-templates/mechanism, where you drop.twigtemplates into predefined slot directories (and can override built-in templates by copying them fromsrc/view/). [4] - Plugin configuration is expressed in
config.ttlusing properties likeskosmos:globalPluginsandskosmos:vocabularyPlugins. [1]
Sources:
[1] Skosmos wiki: “Configuration” (Skosmos 3, config.ttl, skosmos:Configuration, skosmos:Vocabulary) (github-wiki-see.page)
[2] Skosmos 3.0-beta.1 release notes (“Skosmos 3 configuration overhaul”) (github.com)
[3] Skosmos wiki: “Configuration for Skosmos 2” (about.inc, footer.inc, etc.) (github.com)
[4] Skosmos wiki: “Custom templates” (Skosmos 3 custom-templates/*.twig slots + overrides) (github-wiki-see.page)
Citations:
- 1: https://github-wiki-see.page/m/NatLibFi/Skosmos/wiki/Configuration
- 2: https://github.com/NatLibFi/Skosmos/releases?utm_source=openai
- 3: https://github.com/NatLibFi/Skosmos/wiki/Configuration-for-Skosmos-2
- 4: https://github-wiki-see.page/m/NatLibFi/Skosmos/wiki/Custom-templates
🏁 Script executed:
#!/bin/bash
# Check if dockerfile exists in v3.0 by examining the remote repo structure
echo "=== Checking for dockerfiles/Dockerfile.ubuntu in v3.0 ==="
git ls-remote --heads https://github.com/NatLibFi/Skosmos.git | head -1 && \
git archive --remote=https://github.com/NatLibFi/Skosmos.git v3.0 | \
tar -tzf - | grep -E '^dockerfiles/Dockerfile\.ubuntu$' && echo "✓ File exists" || echo "✗ File not found"Repository: kit-data-manager/EVOKS
Length of output: 367
🏁 Script executed:
#!/bin/bash
# Try shallow clone to verify dockerfile
echo "=== Cloning v3.0 (shallow, dockerfile check only) ==="
TEMP_DIR=$(mktemp -d)
git clone --depth 1 --branch v3.0 https://github.com/NatLibFi/Skosmos.git "$TEMP_DIR" 2>&1 | grep -v "^Cloning"
if [ -f "$TEMP_DIR/dockerfiles/Dockerfile.ubuntu" ]; then
echo "✓ dockerfiles/Dockerfile.ubuntu exists in v3.0"
echo ""
echo "=== First 20 lines of Dockerfile.ubuntu ==="
head -20 "$TEMP_DIR/dockerfiles/Dockerfile.ubuntu"
else
echo "✗ dockerfiles/Dockerfile.ubuntu NOT found in v3.0"
echo ""
echo "=== Available dockerfiles ==="
ls -la "$TEMP_DIR/dockerfiles/" 2>/dev/null || echo "No dockerfiles directory"
fi
rm -rf "$TEMP_DIR"Repository: kit-data-manager/EVOKS
Length of output: 1366
Update config.ttl for Skosmos v3.0 breaking changes.
The v3.0 dockerfile path is valid, but this major version bump includes breaking changes to config.ttl that must be addressed:
-
Property renames (if present in your config files):
skosmos:uiHoneypotEnabled→skosmos:feedbackHoneypotEnabledskosmos:uiHoneypotTime→skosmos:feedbackHoneypotTime
-
Plugin configuration overhaul (if using plugins):
- Remove obsolete properties:
skosmos:hasParamPlugin,skosmos:hasPlugin,skosmos:useParamPlugin,skosmos:usePlugin - Use only:
skosmos:globalPlugins(on global Configuration) andskosmos:vocabularyPlugins(per Vocabulary)
- Remove obsolete properties:
-
UI customization (if you've customized the interface):
- Migrate from Twig snippets (
about.inc,footer.inc, etc.) tocustom-templates/*.twigmechanism
- Migrate from Twig snippets (
Review and update ./skosmos-dev/config.ttl and ./skosmos-live/config.ttl accordingly before deploying.
Also applies to: 199-200
🤖 Prompt for AI Agents
In `@docker-compose.yml` around lines 164 - 165, The Skosmos v3.0 docker image in
docker-compose.yml is fine but v3.0 introduces breaking changes in config.ttl;
update ./skosmos-dev/config.ttl and ./skosmos-live/config.ttl to rename
properties skosmos:uiHoneypotEnabled→skosmos:feedbackHoneypotEnabled and
skosmos:uiHoneypotTime→skosmos:feedbackHoneypotTime, remove obsolete plugin
props (skosmos:hasParamPlugin, skosmos:hasPlugin, skosmos:useParamPlugin,
skosmos:usePlugin) and replace them with skosmos:globalPlugins and
skosmos:vocabularyPlugins, and migrate any Twig snippet-based UI customizations
(about.inc, footer.inc, etc.) into custom-templates/*.twig; ensure both config
files are validated before deployment.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.