IQSS / IQSS/dataverse-frontend

Automate the publication of the @iqss/dataverse-design-system package

Open
#140 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

pm.GREI-d-2.7.1 pm.GREI-d-2.7.2
Dominant language
TypeScript
Stars
31
Forks
26
Avg merge
4d 13h
Merged PRs (30d)
4

Description

Overview of the Feature Request

We need to automate the releases of the [@iqss/dataverse-design-system](https://www.npmjs.com/package/@iqss/dataverse-design-system/v/1.0.1?activeTab=versions) npm module.

Currently we are using lerna for the publishing

So the idea is to do a lerna publish automated in the Github Actions to automatically update the package version in the npm registry

Another thing that we'd like to automate is the CHANGELOG

What kind of user is the feature intended for?

Anyone interested in using the dataverse-design-system components library in their projects

What inspired the request

  • #116

What existing behavior do you want changed?

None

Any brand new behavior do you want to add to Dataverse?

Being able to launch a new version of the package automatically using GitHub Actions

Any open or closed issues related to this feature request?

  • #81
  • #23
  • #116

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the repository's current Lerna setup and GitHub Actions configuration, then review related issues #81, #23, and #116. Done means releases of @iqss/dataverse-design-system are automated through GitHub Actions, the package is updated in the npm registry, and the CHANGELOG is automated.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
build-system, ci-cd, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.