Dev/v1.0.1

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -22,31 +22,10 @@ body:
       required: true
   - type: input
     attributes:
-      label: AutoGen version
+      label: sunhat version
       description: What version or commit of the library was used
     validations:
       required: true
-  - type: dropdown
-    attributes:
-      label: Which package was this bug in
-      options:
-        - Core
-        - AgentChat
-        - Extensions
-        - AutoGen Studio
-        - Magentic One
-        - AutoGen Bench
-        - Other
-    validations:
-      required: true
-  - type: input
-    attributes:
-      label: Model used
-      description: If a model was used, please describe it here, indicating whether it is a local model or a cloud-hosted model
-      placeholder: gpt-4, mistral-7B etc
-  - type: input
-    attributes:
-      label: Python version
   - type: input
     attributes:
       label: Operating system

.github/workflows/linux-test.yml

@@ -1,8 +1,8 @@
-name: ubuntu test
+name: CI
 
 on:
   push:
-    branches: [ main, develop ]
+    branches: [ main ]
   pull_request:
     branches: [ main ]
 

.github/workflows/release.yml

@@ -0,0 +1,39 @@
+# .github/workflows/release.yml
+
+name: Release and Publish to npm
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  build-and-publish:
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+
+    environment: release
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+          registry-url: 'https://registry.npmjs.org/'
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - name: Install dependencies and build
+        run: |
+          pnpm install
+          pnpm run build
+
+      - name: Publish to npm
+        run: npm publish --provenance

CHANGELOG.md

@@ -5,6 +5,12 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/).
 
+## [1.0.1] - 2025-11-06
+
+### Added
+- Developer Documents Updated
+- Release Workflow
+
 ## [1.0.0] - 2025-11-03
 
 ### Added

CONTRIBUTE.md

@@ -0,0 +1,29 @@
+## How to Contribute
+
+We welcome contributions from everyone! Contributions to `sunhat` are released under the terms of the [MIT License](https://github.com/sun-protocol/sunhat/blob/main/LICENSE). By submitting a pull request, you agree to license your contribution under this license.
+
+### Reporting Bugs
+
+If you find a bug, please open an issue on our GitHub repository. When you are creating a bug report, please include:
+
+*   A clear and descriptive title.
+*   A detailed description of the problem, including the expected and actual behavior.
+*   Steps to reproduce the bug.
+*   Information about your environment (e.g., operating system, `sunhat` version).
+
+### Suggesting Enhancements
+
+If you have an idea for a new feature or an improvement to an existing one, please open an issue to discuss it. This allows us to coordinate our efforts and prevent duplication of work.
+
+### Pull Request Process
+
+We follow a standard GitHub fork and pull request workflow.
+
+1.  **Fork the repository** to your own GitHub account.
+2.  **Clone your fork** to your local machine.
+3.  **Create a new branch** for your changes. It's good practice to name your branch something descriptive, like `fix-authentication-bug` or `add-user-profiles-feature`.
+4.  **Make your changes**. Ensure that your code adheres to the project's coding standards.
+5.  **Write clear and concise commit messages**. A good commit message explains why a change was made.
+6.  **Push your changes** to your fork on GitHub.
+7.  **Open a pull request** from your branch to the `main` branch of the `sunhat` repository.
+8.  **Respond to feedback**. The project maintainers will review your pull request and may suggest changes. Be open to discussion and be prepared to make further modifications.