Enabled publish (#5)

Author: k2snowman69

.github/CODEOWNERS

@@ -43,5 +43,5 @@ jobs:
         run: npm config set //registry.npmjs.org/:_authToken $NPM_TOKEN
 
       - name: Publish
-        run: npx --no release-it -- --ci --dry-run
+        run: npx --no release-it -- --ci
         continue-on-error: true

.github/workflows/publish.yml

@@ -83,6 +83,15 @@ To create a full integration test for this scenario would be extremely complex,
 
 Instead of constantly being on the backfoot and your CI breaking because another company updated their systems, mocking those dependencies provides a level of stability at the sacrifice of real world resemblance.
 
+### How is this similar/different than enzyme's shallow?
+
+Enzyme's shallow would be able to mock all the imports for you by calling `shallow(<Parent />)`. This library requires you to:
+
+1. Use `jest.unstable_mockModule` to mock all the child components the Parent component is dependent on
+1. Dynamically load the Parent component after mocking all the child components
+
+Theoretically if you mocked all the children a Parent component was dependent on, it would be fairly similar to Enzyme's shallow render.
+
 ## Goals
 
 ### Dependencies

README.md

@@ -58,7 +58,6 @@
     "jest": "^29.0.0",
     "react": "^18.0.0"
   },
-  "private": "true",
   "repository": "github:snowcoders/jest-react-mock-utils",
   "scripts": {
     "build": "concurrently \"npm:build:*\"",