Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: removing free/all filter #359

Merged
merged 1 commit into from
Sep 28, 2023
Merged

feat: removing free/all filter #359

merged 1 commit into from
Sep 28, 2023

Conversation

kiram15
Copy link
Contributor

@kiram15 kiram15 commented Sep 27, 2023

Removal of the free/all filter
Product Decision

Jira

Screenshot 2023-09-27 at 4 19 19 PM Screenshot 2023-09-27 at 4 18 30 PM

Merge checklist:

  • Evaluate how your changes will impact existing consumers (e.g., frontend-app-learner-portal-enterprise, frontend-app-admin-portal, and frontend-app-enterprise-public-catalog). Will consumers safely be able to upgrade to this change without any breaking changes?
  • Ensure your commit message follows the semantic-release conventional commit message format. If your changes include a breaking change, ensure your commit message is explicitly marked as a BREAKING CHANGE so the NPM package is released as such.
  • Once CI is passing, verify the package versions that Lerna will increment to in the Github Action CI workflow logs.
    • Note: This may be found in the "Preview Updated Versions (dry run)" step in the Github Action CI workflow logs.

Post merge:

  • Verify Lerna created a release commit (e.g., chore(release): publish) that incremented versions in relevant package.json and CHANGELOG files, and created Git tags for those versions.
  • Run the Publish from package.json Github Action workflow to publish these new package versions to NPM.
    • This may be triggered by clicking the "Run workflow" option for the master branch.
  • Verify the new package versions were published to NPM (i.e., npm view <package_name> versions --json).
    • Note: There may be a slight delay between when the workflow finished and when NPM reports the package version as being published. If it doesn't appear right away in the above command, try again in a few minutes.

@codecov
Copy link

codecov bot commented Sep 27, 2023

Codecov Report

Merging #359 (23b37e0) into master (e9221d0) will increase coverage by 0.05%.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #359      +/-   ##
==========================================
+ Coverage   78.26%   78.31%   +0.05%     
==========================================
  Files          34       34              
  Lines         667      664       -3     
  Branches      172      170       -2     
==========================================
- Hits          522      520       -2     
+ Misses        132      131       -1     
  Partials       13       13              
Files Coverage Δ
packages/catalog-search/src/SearchFilters.jsx 75.00% <ø> (+1.31%) ⬆️

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e9221d0...23b37e0. Read the comment docs.

@kiram15 kiram15 requested a review from a team September 27, 2023 22:21
@kiram15 kiram15 merged commit f187fbd into master Sep 28, 2023
8 checks passed
@kiram15 kiram15 deleted the kiram15/ENT-7747-1 branch September 28, 2023 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants