WeSearch

Publishing One Package to Five Registries with GitHub Actions

·10 min read · 0 reactions · 0 comments · 35 views
Publishing One Package to Five Registries with GitHub Actions
TL;DR · WeSearch summary

A new open-source project called eu-vat-rates-data provides a reliable dataset of EU VAT rates published across five programming language registries. This initiative aims to simplify access to VAT data by bundling it into native packages, eliminating the need for developers to handle network calls or parsing. The data is sourced from the European Commission's official database and is updated daily, ensuring accuracy and ease of use for developers in various ecosystems.

Key facts
About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

Original article
DEV.to (Top)
Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherDEV.to (Top)
Canonical URLhttps://dev.to/iurii_rogulia/publishing-one-package-to-five-registries-with-github-actions-3p7c
Publication timeWed, 03 Jun 2026 10:00:37 +0000
Retrieval time2026-06-03T10:12:01.667Z
Last seen2026-06-03T10:12:01.667Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster58_sI0ufgSgQ
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3561015) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Iurii Rogulia Posted on Jun 3 • Originally published at iurii.rogulia.fi Publishing One Package to Five Registries with GitHub Actions #typescript #python #php #go Every developer building for European markets hits the same wall eventually. EU VAT rates are public data — the European Commission publishes them — but getting that data into your codebase reliably is a mess. You hardcode the rates, they change, your invoices are wrong.

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from DEV.to (Top)