Skip to content

build(ngx-core):v19.0.0 #343

Merged
IbenTesara merged 1 commit intomasterfrom
release/ngx-core/v19.0.0
Dec 16, 2024
Merged

build(ngx-core):v19.0.0 #343
IbenTesara merged 1 commit intomasterfrom
release/ngx-core/v19.0.0

Conversation

@IbenTesara
Copy link
Copy Markdown
Contributor

@IbenTesara IbenTesara commented Dec 16, 2024

Description
Release v19.0.0

Requirements

  • Correct label have been assigned
  • Project has been assigned
  • Milestone has been (created/)assigned

@IbenTesara IbenTesara added publish These tickets are related to publishing new versions of packages. ngx-core @studiohyperdrive/ngx-core labels Dec 16, 2024
@IbenTesara IbenTesara added this to the hyperdrive-open-source milestone Dec 16, 2024
@IbenTesara IbenTesara self-assigned this Dec 16, 2024
Copy link
Copy Markdown
Contributor

@WHeirstrate WHeirstrate left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't the target branch be feat/ngx-core/149-setup-shared-library instead of master? Now it looks like you try to both release and implement changes.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Should this markdown file exist?
  2. If so, should this not add a little more information as to the purpose of these Angular libs? Perhaps a link to the Angular documentation in a setup section?

Comment thread libs/angular/core/package.json Outdated
"version": "19.0.0",
"description": "A library of core functionality used by the Studio Hyperdrive NGX packages.",
"keywords": [
"angular"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps Studio Hyperdrive, StudioHyperdrive, and ngx-tools could be additional keywords?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional thought: maybe ngx-tools can be a keyword of every package as to connect them more easily through npm?

@IbenTesara IbenTesara changed the base branch from master to feat/ngx-core/149-setup-shared-library December 16, 2024 14:18
@IbenTesara IbenTesara changed the title Release/ngx core/v19.0.0 build(ngx-core):v19.0.0 Dec 16, 2024
@IbenTesara IbenTesara force-pushed the release/ngx-core/v19.0.0 branch from 10d47b2 to 9ccfcb6 Compare December 16, 2024 14:20
@IbenTesara IbenTesara force-pushed the feat/ngx-core/149-setup-shared-library branch from e73af6d to 4d1d7b4 Compare December 16, 2024 14:24
@IbenTesara IbenTesara force-pushed the release/ngx-core/v19.0.0 branch from 9ccfcb6 to dd85b93 Compare December 16, 2024 14:24
@IbenTesara IbenTesara changed the base branch from feat/ngx-core/149-setup-shared-library to master December 16, 2024 14:29
@IbenTesara IbenTesara force-pushed the release/ngx-core/v19.0.0 branch from dd85b93 to bc1af31 Compare December 16, 2024 14:30
@IbenTesara IbenTesara merged commit a227ad7 into master Dec 16, 2024
@reunefe reunefe deleted the release/ngx-core/v19.0.0 branch January 9, 2025 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ngx-core @studiohyperdrive/ngx-core publish These tickets are related to publishing new versions of packages.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants